From: Johannes Berg <johannes@sipsolutions•net>
To: Randy Dunlap <rdunlap@infradead•org>,
Bert Karwatzki <spasswolf@web•de>,
linux-wireless@vger•kernel.org
Cc: linux-kernel@vger•kernel.org, linux-next@vger•kernel.org,
Jason Xing <kerneljasonxing@gmail•com>
Subject: Re: [PATCH] wifi: add sk_requests_wifi_status()
Date: Wed, 21 May 2025 09:02:07 +0200 [thread overview]
Message-ID: <545397842b6079ac0d51cfa8c49d5b2f13c14f58.camel@sipsolutions.net> (raw)
In-Reply-To: <8cc4c232-c7cd-4dec-97c8-3573b5e471c2@infradead.org>
On Tue, 2025-05-20 at 15:57 -0700, Randy Dunlap wrote:
...
> That is usually spelled
> Suggested-by:
...
> Missing indentation on the line above.
...
I'll just fix that - will apply it now. Maybe also change the subject,
since really it's about checking the socket flags properly, the main
feature isn't adding the function :)
johannes
next prev parent reply other threads:[~2025-05-21 7:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-20 22:34 [PATCH] wifi: add sk_requests_wifi_status() Bert Karwatzki
2025-05-20 22:57 ` Randy Dunlap
2025-05-21 7:02 ` Johannes Berg [this message]
2025-05-21 7:23 ` Jason Xing
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=545397842b6079ac0d51cfa8c49d5b2f13c14f58.camel@sipsolutions.net \
--to=johannes@sipsolutions$(echo .)net \
--cc=kerneljasonxing@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-wireless@vger$(echo .)kernel.org \
--cc=rdunlap@infradead$(echo .)org \
--cc=spasswolf@web$(echo .)de \
/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