Linux CAN drivers development
 help / color / mirror / Atom feed
From: Charles Han <hanchunchao@inspur.com>
To: <mkl@pengutronix.de>, <manivannan.sadhasivam@linaro.org>,
	<thomas.kopp@microchip.com>, <mailhol.vincent@wanadoo.fr>,
	<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
	<cem@kernel.org>, <djwong@kernel.org>, <corbet@lwn.net>
Cc: <linux-can@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <linux-xfs@vger.kernel.org>,
	<linux-doc@vger.kernel.org>, Charles Han <hanchunchao@inspur.com>
Subject: [PATCH] Documentation: Remove repeated word in docs
Date: Thu, 6 Feb 2025 17:15:29 +0800	[thread overview]
Message-ID: <20250206091530.4826-1-hanchunchao@inspur.com> (raw)

Remove the repeated word "to" docs.

Signed-off-by: Charles Han <hanchunchao@inspur.com>
---
 .../devicetree/bindings/net/can/microchip,mcp251xfd.yaml        | 2 +-
 Documentation/filesystems/xfs/xfs-online-fsck-design.rst        | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/devicetree/bindings/net/can/microchip,mcp251xfd.yaml b/Documentation/devicetree/bindings/net/can/microchip,mcp251xfd.yaml
index 2a98b26630cb..c155c9c6db39 100644
--- a/Documentation/devicetree/bindings/net/can/microchip,mcp251xfd.yaml
+++ b/Documentation/devicetree/bindings/net/can/microchip,mcp251xfd.yaml
@@ -40,7 +40,7 @@ properties:
 
   microchip,rx-int-gpios:
     description:
-      GPIO phandle of GPIO connected to to INT1 pin of the MCP251XFD, which
+      GPIO phandle of GPIO connected to INT1 pin of the MCP251XFD, which
       signals a pending RX interrupt.
     maxItems: 1
 
diff --git a/Documentation/filesystems/xfs/xfs-online-fsck-design.rst b/Documentation/filesystems/xfs/xfs-online-fsck-design.rst
index 12aa63840830..994f9e5638ee 100644
--- a/Documentation/filesystems/xfs/xfs-online-fsck-design.rst
+++ b/Documentation/filesystems/xfs/xfs-online-fsck-design.rst
@@ -4521,7 +4521,7 @@ Both online and offline repair can use this strategy.
 | For this second effort, the ondisk parent pointer format as originally   |
 | proposed was ``(parent_inum, parent_gen, dirent_pos) → (dirent_name)``.  |
 | The format was changed during development to eliminate the requirement   |
-| of repair tools needing to to ensure that the ``dirent_pos`` field       |
+| of repair tools needing to ensure that the ``dirent_pos`` field       |
 | always matched when reconstructing a directory.                          |
 |                                                                          |
 | There were a few other ways to have solved that problem:                 |
-- 
2.43.0


             reply	other threads:[~2025-02-06  9:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-06  9:15 Charles Han [this message]
2025-02-06  9:30 ` [PATCH] Documentation: Remove repeated word in docs Marc Kleine-Budde
2025-02-06 10:56 ` Vincent Mailhol
2025-02-07  1:25   ` Bagas Sanjaya

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250206091530.4826-1-hanchunchao@inspur.com \
    --to=hanchunchao@inspur.com \
    --cc=cem@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=djwong@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=mailhol.vincent@wanadoo.fr \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=mkl@pengutronix.de \
    --cc=robh@kernel.org \
    --cc=thomas.kopp@microchip.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox