All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jayaraj Devaraj <jayarajdmit@gmail.com>
To: Parthiban Veerasooran <parthiban.veerasooran@microchip.com>
Cc: netdev@vger.kernel.org, linux-doc@vger.kernel.org,
	Jakub Kicinski <kuba@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Jayaraj Devaraj <jayarajdmit@gmail.com>
Subject: [PATCH net-next] docs: oa-tc6-framework: Fix typo in SYNC bit description
Date: Tue,  6 Oct 2026 01:11:35 +0530	[thread overview]
Message-ID: <20261005194135.64584-1-jayarajdmit@gmail.com> (raw)

Fix a missing space in the SYNC bit
description: "bitin" should
be "bit in".

Signed-off-by: Jayaraj Devaraj <jayarajdmit@gmail.com>
---
 Documentation/networking/oa-tc6-framework.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/networking/oa-tc6-framework.rst b/Documentation/networking/oa-tc6-framework.rst
index 0feda2f9d..2545ef694 100644
--- a/Documentation/networking/oa-tc6-framework.rst
+++ b/Documentation/networking/oa-tc6-framework.rst
@@ -278,7 +278,7 @@ SYNC (Bit 29) - Configuration Synchronized flag. This bit reflects the
                 register (see Table 12). A zero indicates that the MAC-PHY
                 configuration may not be as expected by the SPI host.
                 Following configuration, the SPI host sets the
-                corresponding bitin the configuration register which is
+                corresponding bit in the configuration register which is
                 reflected in this field.
 
 RCA (Bit 28..24) - Receive Chunks Available. The RCA field indicates to
-- 
2.34.1


             reply	other threads:[~2026-10-05 19:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-05 19:41 Jayaraj Devaraj [this message]
2026-10-09  2:00 ` [PATCH net-next] docs: oa-tc6-framework: Fix typo in SYNC bit description patchwork-bot+netdevbpf

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=20261005194135.64584-1-jayarajdmit@gmail.com \
    --to=jayarajdmit@gmail.com \
    --cc=corbet@lwn.net \
    --cc=kuba@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=parthiban.veerasooran@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.