From nobody Tue Apr 7 14:56:59 2026 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id CEC29ECAAA3 for ; Fri, 26 Aug 2022 14:33:20 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1344486AbiHZOdT (ORCPT ); Fri, 26 Aug 2022 10:33:19 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36870 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1344477AbiHZOdQ (ORCPT ); Fri, 26 Aug 2022 10:33:16 -0400 Received: from smtpout140.security-mail.net (smtpout140.security-mail.net [85.31.212.148]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7EE6C81B2E for ; Fri, 26 Aug 2022 07:33:14 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by fx408.security-mail.net (Postfix) with ESMTP id F394B1B7B0B9 for ; Fri, 26 Aug 2022 16:33:12 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kalray.eu; s=sec-sig-email; t=1661524393; bh=bMQHm9FHKP0igbY8RmVj0GPPueBKFqVXF4ImoKEiKe8=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=NkoEn6d4r2qH2ThXa2TctibGJFGK2gUvRsQJdSfv3Nvc531ztd0wBBMNo4hU55KLo lknereEu0PLmRHmx687muxxcYPjWTownIxCBfh6Xly18oR31ZDMXvH+aueNZmS5meG d4tuejYV0fQr316PDsDi3kefZ4eF63DIANhIdyzs= Received: from fx408 (localhost [127.0.0.1]) by fx408.security-mail.net (Postfix) with ESMTP id A102B1B7B02C; Fri, 26 Aug 2022 16:33:12 +0200 (CEST) X-Virus-Scanned: E-securemail Secumail-id: <153b0.6308d9a8.24f67.0> Received: from zimbra2.kalray.eu (unknown [217.181.231.53]) by fx408.security-mail.net (Postfix) with ESMTPS id 2599C1B7B081; Fri, 26 Aug 2022 16:33:12 +0200 (CEST) Received: from zimbra2.kalray.eu (localhost [127.0.0.1]) by zimbra2.kalray.eu (Postfix) with ESMTPS id 0671E27E02FA; Fri, 26 Aug 2022 16:33:12 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by zimbra2.kalray.eu (Postfix) with ESMTP id E0BA127E0392; Fri, 26 Aug 2022 16:33:11 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.10.3 zimbra2.kalray.eu E0BA127E0392 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kalray.eu; s=32AE1B44-9502-11E5-BA35-3734643DEF29; t=1661524391; bh=c3cPqQyjOphfQrx1xunIlqGBObVLkJW/2AnFPcY3L0w=; h=From:To:Date:Message-Id; b=b5BZVyR73wo/2888srxtxtuDqY+147RUm2PlmuisD0mqcYOlGSt7VZzK0RQI30GNs FaBGRK650rSvR2/50JNzC4l0kTxPByifRtSBag4MIwdbLZmguNsPmYIr/FQCSQ/9zW KcA8rwjx9Nbx+2a4V6bOdnB664RkcdKaKobzw+yQ= Received: from zimbra2.kalray.eu ([127.0.0.1]) by localhost (zimbra2.kalray.eu [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id sS82OsDCsIuf; Fri, 26 Aug 2022 16:33:11 +0200 (CEST) Received: from tellis.lin.mbt.kalray.eu (unknown [192.168.36.206]) by zimbra2.kalray.eu (Postfix) with ESMTPSA id C59A227E02FA; Fri, 26 Aug 2022 16:33:11 +0200 (CEST) From: Jules Maselbas To: linux-kernel@vger.kernel.org Cc: Jules Maselbas , Bagas Sanjaya , Jonathan Corbet , linux-doc@vger.kernel.org Subject: [PATCH v2] Remove duplicated 'the' across the whole documentation Date: Fri, 26 Aug 2022 16:33:00 +0200 Message-Id: <20220826143300.6794-1-jmaselbas@kalray.eu> X-Mailer: git-send-email 2.17.1 In-Reply-To: <20220826095321.21548-1-jmaselbas@kalray.eu> References: <20220826095321.21548-1-jmaselbas@kalray.eu> X-Virus-Scanned: by Secumail Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Remove duplicated 'the' across the whole documentation CC: Bagas Sanjaya CC: Jonathan Corbet CC: linux-doc@vger.kernel.org Signed-off-by: Jules Maselbas Acked-by: Randy Dunlap --- in v2: - also remove the second 'the' in one sentence as suggested by Bagas Sanjaya Documentation/admin-guide/kdump/vmcoreinfo.rst | 2 +- Documentation/bpf/map_cgroup_storage.rst | 4 ++-- Documentation/core-api/cpu_hotplug.rst | 3 +-- Documentation/driver-api/isa.rst | 2 +- Documentation/filesystems/caching/backend-api.rst | 2 +- Documentation/locking/seqlock.rst | 2 +- Documentation/sphinx/cdomain.py | 2 +- 7 files changed, 8 insertions(+), 9 deletions(-) diff --git a/Documentation/admin-guide/kdump/vmcoreinfo.rst b/Documentation= /admin-guide/kdump/vmcoreinfo.rst index 8419019b6a88..6726f439958c 100644 --- a/Documentation/admin-guide/kdump/vmcoreinfo.rst +++ b/Documentation/admin-guide/kdump/vmcoreinfo.rst @@ -200,7 +200,7 @@ prb =20 A pointer to the printk ringbuffer (struct printk_ringbuffer). This may be pointing to the static boot ringbuffer or the dynamically -allocated ringbuffer, depending on when the the core dump occurred. +allocated ringbuffer, depending on when the core dump occurred. Used by user-space tools to read the active kernel log buffer. =20 printk_rb_static diff --git a/Documentation/bpf/map_cgroup_storage.rst b/Documentation/bpf/m= ap_cgroup_storage.rst index cab9543017bf..8e5fe532c07e 100644 --- a/Documentation/bpf/map_cgroup_storage.rst +++ b/Documentation/bpf/map_cgroup_storage.rst @@ -31,7 +31,7 @@ The map uses key of type of either ``__u64 cgroup_inode_i= d`` or }; =20 ``cgroup_inode_id`` is the inode id of the cgroup directory. -``attach_type`` is the the program's attach type. +``attach_type`` is the program's attach type. =20 Linux 5.9 added support for type ``__u64 cgroup_inode_id`` as the key type. When this key type is used, then all attach types of the particular cgroup= and @@ -155,7 +155,7 @@ However, the BPF program can still only associate with = one map of each type ``BPF_MAP_TYPE_CGROUP_STORAGE`` or more than one ``BPF_MAP_TYPE_PERCPU_CGROUP_STORAGE``. =20 -In all versions, userspace may use the the attach parameters of cgroup and +In all versions, userspace may use the attach parameters of cgroup and attach type pair in ``struct bpf_cgroup_storage_key`` as the key to the BP= F map APIs to read or update the storage for a given attachment. For Linux 5.9 attach type shared storages, only the first value in the struct, cgroup in= ode diff --git a/Documentation/core-api/cpu_hotplug.rst b/Documentation/core-ap= i/cpu_hotplug.rst index c6f4ba2fb32d..c326f4a86d34 100644 --- a/Documentation/core-api/cpu_hotplug.rst +++ b/Documentation/core-api/cpu_hotplug.rst @@ -560,8 +560,7 @@ available: * cpuhp_state_remove_instance(state, node) * cpuhp_state_remove_instance_nocalls(state, node) =20 -The arguments are the same as for the the cpuhp_state_add_instance*() -variants above. +The arguments are the same as for cpuhp_state_add_instance*() variants abo= ve. =20 The functions differ in the way how the installed callbacks are treated: =20 diff --git a/Documentation/driver-api/isa.rst b/Documentation/driver-api/is= a.rst index def4a7b690b5..3df1b1696524 100644 --- a/Documentation/driver-api/isa.rst +++ b/Documentation/driver-api/isa.rst @@ -100,7 +100,7 @@ I believe platform_data is available for this, but if r= ather not, moving the isa_driver pointer to the private struct isa_dev is ofcourse fine as well. =20 -Then, if the the driver did not provide a .match, it matches. If it did, +Then, if the driver did not provide a .match, it matches. If it did, the driver match() method is called to determine a match. =20 If it did **not** match, dev->platform_data is reset to indicate this to diff --git a/Documentation/filesystems/caching/backend-api.rst b/Documentat= ion/filesystems/caching/backend-api.rst index d7507becf674..3a199fc50828 100644 --- a/Documentation/filesystems/caching/backend-api.rst +++ b/Documentation/filesystems/caching/backend-api.rst @@ -122,7 +122,7 @@ volumes, calling:: to tell fscache that a volume has been withdrawn. This waits for all outstanding accesses on the volume to complete before returning. =20 -When the the cache is completely withdrawn, fscache should be notified by +When the cache is completely withdrawn, fscache should be notified by calling:: =20 void fscache_relinquish_cache(struct fscache_cache *cache); diff --git a/Documentation/locking/seqlock.rst b/Documentation/locking/seql= ock.rst index 64405e5da63e..bfda1a5fecad 100644 --- a/Documentation/locking/seqlock.rst +++ b/Documentation/locking/seqlock.rst @@ -39,7 +39,7 @@ as the writer can invalidate a pointer that the reader is= following. Sequence counters (``seqcount_t``) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 -This is the the raw counting mechanism, which does not protect against +This is the raw counting mechanism, which does not protect against multiple writers. Write side critical sections must thus be serialized by an external lock. =20 diff --git a/Documentation/sphinx/cdomain.py b/Documentation/sphinx/cdomain= .py index ca8ac9e59ded..a7d1866e72ff 100644 --- a/Documentation/sphinx/cdomain.py +++ b/Documentation/sphinx/cdomain.py @@ -151,7 +151,7 @@ class CObject(Base_CObject): def handle_func_like_macro(self, sig, signode): u"""Handles signatures of function-like macros. =20 - If the objtype is 'function' and the the signature ``sig`` is a + If the objtype is 'function' and the signature ``sig`` is a function-like macro, the name of the macro is returned. Otherwise ``False`` is returned. """ =20 --=20 2.17.1