netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: pull-request: wireless-2022-10-13
Date: Thu, 13 Oct 2022 09:29:09 -0700	[thread overview]
Message-ID: <20221013092909.2a15c52e@kernel.org> (raw)
In-Reply-To: <e012c43378b21fe9a9753d3d1a1f550df8de60a0.camel@sipsolutions.net>

On Thu, 13 Oct 2022 18:13:00 +0200 Johannes Berg wrote:
> FWIW, it's harmless, but we do need to silence the sparse warning. I'll
> add a follow-up patch for our next pull request, unless you want it
> quickly, then I can send it to you directly?

Next PR is perfectly fine, I reckon.

      reply	other threads:[~2022-10-13 16:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-13 10:04 pull-request: wireless-2022-10-13 Johannes Berg
2022-10-13 15:32 ` Jakub Kicinski
2022-10-13 15:32 ` Jakub Kicinski
2022-10-13 16:13   ` Johannes Berg
2022-10-13 16:29     ` Jakub Kicinski [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=20221013092909.2a15c52e@kernel.org \
    --to=kuba@kernel.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).