Linux wireless drivers development
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] wifi: cfg80211: wext: Correct spelling in iw_handler.h
Date: Tue, 3 Sep 2024 09:25:58 +0100	[thread overview]
Message-ID: <20240903082558.GQ23170@kernel.org> (raw)
In-Reply-To: <edb3a22af9246ad6b6d71d53844bf76249c77e13.camel@sipsolutions.net>

On Mon, Sep 02, 2024 at 11:11:11AM +0200, Johannes Berg wrote:
> On Mon, 2024-09-02 at 10:01 +0100, Simon Horman wrote:
> > > But is it worth it at all? This stuff is totally on the way out, so all
> > > the thing about "proven a reasonably good design", well, didn't really
> > > pan out in practice...
> > 
> > I think if the text is there it may as well be correct.
> > But if you prefer to leave it as is, then we can drop this topic.
> 
> Sure, that's fair, I'm happy to apply patches updating the
> grammar/spelling by itself. No need to go into full rewrite and/or
> historic debates about the design :)

Thanks, I agree.

I have sent a v2, which addresses the grammar issue that you flagged.

https://lore.kernel.org/linux-wireless/20240903-wifi-spell-v2-1-bfcf7062face@kernel.org/

I did look for other grammar issues on other lines that are already
updated by that patch: you can get a laugh when you find something obvious.

I didn't check any further, because this seems to be enough for now.
But I can if you like.

      reply	other threads:[~2024-09-03  8:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-29 16:03 [PATCH] wifi: cfg80211: wext: Correct spelling in iw_handler.h Simon Horman
2024-08-29 16:07 ` Johannes Berg
2024-09-02  9:01   ` Simon Horman
2024-09-02  9:11     ` Johannes Berg
2024-09-03  8:25       ` 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=20240903082558.GQ23170@kernel.org \
    --to=horms@kernel.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.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