From: Jiri Pirko <jiri@resnulli•us>
To: Antony Antony <antony@phenome•org>
Cc: netdev@vger•kernel.org,
Steffen Klassert <steffen.klassert@secunet•com>,
Herbert Xu <herbert@gondor•apana.org.au>
Subject: Re: [PATCH ipsec] xfrm: Correct spelling mistake in xfrm.h comment
Date: Fri, 26 Apr 2024 13:23:04 +0200 [thread overview]
Message-ID: <ZiuOmLqOXfPXwzRd@nanopsycho> (raw)
In-Reply-To: <Zit-sTZoYp_JnQfd@Antony2201.local>
Fri, Apr 26, 2024 at 12:15:13PM CEST, antony@phenome•org wrote:
>From: Antony Antony <antony.antony@secunet•com>
>
>A spelling error was found in the comment section of
>include/uapi/linux/xfrm.h. Since this header file is copied to many
>userspace programs and undergoes Debian spellcheck, it's preferable to
>fix it in upstream rather than downstream having exceptions.
>
>This commit fixes the spelling mistake.
>
>Fixes: df71837d5024 ("[LSM-IPSec]: Security association restriction.")
>Signed-off-by: Antony Antony <antony.antony@secunet•com>
Reviewed-by: Jiri Pirko <jiri@nvidia•com>
next prev parent reply other threads:[~2024-04-26 11:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 10:15 [PATCH ipsec] xfrm: Correct spelling mistake in xfrm.h comment Antony Antony
2024-04-26 11:23 ` Jiri Pirko [this message]
2024-04-30 6:20 ` Steffen Klassert
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=ZiuOmLqOXfPXwzRd@nanopsycho \
--to=jiri@resnulli$(echo .)us \
--cc=antony@phenome$(echo .)org \
--cc=herbert@gondor$(echo .)apana.org.au \
--cc=netdev@vger$(echo .)kernel.org \
--cc=steffen.klassert@secunet$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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