From: Simon Horman <horms@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: netdev@vger.kernel.org, Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org, Kalle Valo <kvalo@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH] wifi: cfg80211: fix spelling & punctutation
Date: Thu, 14 Dec 2023 17:29:45 +0000 [thread overview]
Message-ID: <20231214172945.GP5817@kernel.org> (raw)
In-Reply-To: <20231214172700.GO5817@kernel.org>
On Thu, Dec 14, 2023 at 05:27:05PM +0000, Simon Horman wrote:
> On Tue, Dec 12, 2023 at 08:35:58PM -0800, Randy Dunlap wrote:
> > Correct spelling and run-on sentences.
> >
> > Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> > Cc: Johannes Berg <johannes@sipsolutions.net>
> > Cc: linux-wireless@vger.kernel.org
> > Cc: Kalle Valo <kvalo@kernel.org>
> > Cc: "David S. Miller" <davem@davemloft.net>
> > Cc: Eric Dumazet <edumazet@google.com>
> > Cc: Jakub Kicinski <kuba@kernel.org>
> > Cc: Paolo Abeni <pabeni@redhat.com>
>
> Thanks Randy,
>
> These changes look correct to me.
>
> FWIIW, codespell does not flag any non-false-positive spelling errors
> both with and without this patch.
Sorry, I misspoke there.
I now see that with this patch applied codespell no
longer flags any non-false-positive spelling errors
in this file. And that relevant is misspelt without this patch.
> Reviewed-by: Simon Horman <horms@kernel.org>
prev parent reply other threads:[~2023-12-14 17:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 4:35 [PATCH] wifi: cfg80211: fix spelling & punctutation Randy Dunlap
2023-12-14 17:27 ` Simon Horman
2023-12-14 17:29 ` Simon Horman [this message]
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=20231214172945.GP5817@kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rdunlap@infradead.org \
/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