From: Randy Dunlap <rdunlap@infradead.org>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fddi: skfp: Rudimentary spello fixes
Date: Thu, 25 Mar 2021 10:22:49 -0700 [thread overview]
Message-ID: <c75e92a7-077c-44ee-4fef-1d5efdb89ff4@infradead.org> (raw)
In-Reply-To: <20210325070835.32041-1-unixbhaskar@gmail.com>
On 3/25/21 12:08 AM, Bhaskar Chowdhury wrote:
>
> s/autohorized/authorized/
> s/recsource/resource/
> s/measuered/measured/
> sauthoriziation/authorization/
s/
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> drivers/net/fddi/skfp/h/smt.h | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/net/fddi/skfp/h/smt.h b/drivers/net/fddi/skfp/h/smt.h
> index a0dbc0f57a55..8d104f13e2c3 100644
> --- a/drivers/net/fddi/skfp/h/smt.h
> +++ b/drivers/net/fddi/skfp/h/smt.h
> @@ -411,7 +411,7 @@ struct smt_p_reason {
> #define SMT_RDF_ILLEGAL 0x00000005 /* read only (PMF) */
> #define SMT_RDF_NOPARAM 0x6 /* parameter not supported (PMF) */
> #define SMT_RDF_RANGE 0x8 /* out of range */
> -#define SMT_RDF_AUTHOR 0x9 /* not autohorized */
> +#define SMT_RDF_AUTHOR 0x9 /* not authorized */
> #define SMT_RDF_LENGTH 0x0a /* length error */
> #define SMT_RDF_TOOLONG 0x0b /* length error */
> #define SMT_RDF_SBA 0x0d /* SBA denied */
> @@ -450,7 +450,7 @@ struct smt_p_version {
>
> struct smt_p_0015 {
> struct smt_para para ; /* generic parameter header */
> - u_int res_type ; /* recsource type */
> + u_int res_type ; /* resource type */
> } ;
>
> #define SYNC_BW 0x00000001L /* Synchronous Bandwidth */
> @@ -489,7 +489,7 @@ struct smt_p_0017 {
> struct smt_p_0018 {
> struct smt_para para ; /* generic parameter header */
> int sba_ov_req ; /* total sync bandwidth req for overhead*/
> -} ; /* measuered in bytes per T_Neg */
> +} ; /* measured in bytes per T_Neg */
>
> /*
> * P19 : SBA Allocation Address
> @@ -562,7 +562,7 @@ struct smt_p_fsc {
> #define FSC_TYPE2 2 /* Special A/C indicator forwarding */
>
> /*
> - * P00 21 : user defined authoriziation (see pmf.c)
> + * P00 21 : user defined authorization (see pmf.c)
> */
> #define SMT_P_AUTHOR 0x0021
>
> --
--
~Randy
next prev parent reply other threads:[~2021-03-25 17:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 7:08 Bhaskar Chowdhury
2021-03-25 17:22 ` Randy Dunlap [this message]
2021-03-26 0:09 ` David Miller
2021-03-26 5:37 ` kinldy see the V2 ..just sent " Bhaskar Chowdhury
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=c75e92a7-077c-44ee-4fef-1d5efdb89ff4@infradead.org \
--to=rdunlap@infradead.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=unixbhaskar@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
all inboxes | Powered by JetHome®