linux-sctp.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
	 "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	 Jakub Kicinski <kuba@kernel.org>,
	Paolo Abeni <pabeni@redhat.com>,
	 Alexandra Winter <wintera@linux.ibm.com>,
	 Thorsten Winkler <twinkler@linux.ibm.com>,
	David Ahern <dsahern@kernel.org>,
	 Jay Vosburgh <jv@jvosburgh.net>,
	Andy Gospodarek <andy@greyhouse.net>,
	 Subash Abhinov Kasiviswanathan <quic_subashab@quicinc.com>,
	 Sean Tranchetti <quic_stranche@quicinc.com>,
	 Paul Moore <paul@paul-moore.com>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	 Jamal Hadi Salim <jhs@mojatatu.com>,
	Cong Wang <xiyou.wangcong@gmail.com>,
	 Jiri Pirko <jiri@resnulli.us>,
	 Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
	 Xin Long <lucien.xin@gmail.com>, Martin Schiller <ms@dev.tdt.de>
Cc: netdev@vger.kernel.org, linux-s390@vger.kernel.org,
	 linux-security-module@vger.kernel.org,
	linux-sctp@vger.kernel.org,  linux-x25@vger.kernel.org
Subject: [PATCH net-next 01/13] packet: Correct spelling in if_packet.h
Date: Thu, 22 Aug 2024 13:57:22 +0100	[thread overview]
Message-ID: <20240822-net-spell-v1-1-3a98971ce2d2@kernel.org> (raw)
In-Reply-To: <20240822-net-spell-v1-0-3a98971ce2d2@kernel.org>

Correct spelling in if_packet.h
As reported by codespell.

Cc: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Signed-off-by: Simon Horman <horms@kernel.org>
---
 include/uapi/linux/if_packet.h | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/include/uapi/linux/if_packet.h b/include/uapi/linux/if_packet.h
index 9efc42382fdb..1d2718dd9647 100644
--- a/include/uapi/linux/if_packet.h
+++ b/include/uapi/linux/if_packet.h
@@ -230,8 +230,8 @@ struct tpacket_hdr_v1 {
 	 * ts_first_pkt:
 	 *		Is always the time-stamp when the block was opened.
 	 *		Case a)	ZERO packets
-	 *			No packets to deal with but atleast you know the
-	 *			time-interval of this block.
+	 *			No packets to deal with but at least you know
+	 *			the time-interval of this block.
 	 *		Case b) Non-zero packets
 	 *			Use the ts of the first packet in the block.
 	 *
@@ -265,7 +265,8 @@ enum tpacket_versions {
    - struct tpacket_hdr
    - pad to TPACKET_ALIGNMENT=16
    - struct sockaddr_ll
-   - Gap, chosen so that packet data (Start+tp_net) alignes to TPACKET_ALIGNMENT=16
+   - Gap, chosen so that packet data (Start+tp_net) aligns to
+     TPACKET_ALIGNMENT=16
    - Start+tp_mac: [ Optional MAC header ]
    - Start+tp_net: Packet data, aligned to TPACKET_ALIGNMENT=16.
    - Pad to align to TPACKET_ALIGNMENT=16

-- 
2.43.0


  reply	other threads:[~2024-08-22 12:57 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-22 12:57 [PATCH net-next 00/13] net: header and core spelling corrections Simon Horman
2024-08-22 12:57 ` Simon Horman [this message]
2024-08-23 12:42   ` [PATCH net-next 01/13] packet: Correct spelling in if_packet.h Willem de Bruijn
2024-08-22 12:57 ` [PATCH net-next 02/13] s390/iucv: Correct spelling in iucv.h Simon Horman
2024-08-22 12:57 ` [PATCH net-next 03/13] ip_tunnel: Correct spelling in ip_tunnels.h Simon Horman
2024-08-22 12:57 ` [PATCH net-next 04/13] ipv6: Correct spelling in ipv6.h Simon Horman
2024-08-22 12:57 ` [PATCH net-next 05/13] bonding: Correct spelling in headers Simon Horman
2024-08-22 12:57 ` [PATCH net-next 06/13] net: qualcomm: rmnet: Correct spelling in if_rmnet.h Simon Horman
2024-08-23  5:07   ` Subash Abhinov Kasiviswanathan (KS)
2024-08-22 12:57 ` [PATCH net-next 07/13] netlabel: Correct spelling in netlabel.h Simon Horman
2024-08-22 12:57 ` [PATCH net-next 08/13] NFC: Correct spelling in headers Simon Horman
2024-08-23 13:40   ` Krzysztof Kozlowski
2024-08-22 12:57 ` [PATCH net-next 09/13] net: sched: " Simon Horman
2024-08-22 12:57 ` [PATCH net-next 10/13] sctp: " Simon Horman
2024-08-22 14:01   ` Xin Long
2024-08-22 12:57 ` [PATCH net-next 11/13] x25: Correct spelling in x25.h Simon Horman
2024-08-23  5:27   ` Martin Schiller
2024-08-22 12:57 ` [PATCH net-next 12/13] net: Correct spelling in headers Simon Horman
2024-08-26 16:45   ` Jakub Kicinski
2024-08-27  8:25     ` Simon Horman
2024-08-22 12:57 ` [PATCH net-next 13/13] net: Correct spelling in net/core Simon Horman
2024-08-25  7:52 ` [PATCH net-next 00/13] net: header and core spelling corrections Philipp Stanner
2024-08-25  8:06   ` Krzysztof Kozlowski
2024-08-25  8:54   ` Simon Horman
2024-08-26 16:50 ` 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=20240822-net-spell-v1-1-3a98971ce2d2@kernel.org \
    --to=horms@kernel.org \
    --cc=andy@greyhouse.net \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=jv@jvosburgh.net \
    --cc=krzk@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux-sctp@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=linux-x25@vger.kernel.org \
    --cc=lucien.xin@gmail.com \
    --cc=marcelo.leitner@gmail.com \
    --cc=ms@dev.tdt.de \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=paul@paul-moore.com \
    --cc=quic_stranche@quicinc.com \
    --cc=quic_subashab@quicinc.com \
    --cc=twinkler@linux.ibm.com \
    --cc=willemdebruijn.kernel@gmail.com \
    --cc=wintera@linux.ibm.com \
    --cc=xiyou.wangcong@gmail.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;
as well as URLs for NNTP newsgroup(s).