From: Jakub Kicinski <kuba@kernel.org>
To: Kalle Valo <kvalo@kernel.org>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: pull-request: wireless-next-2024-09-11
Date: Wed, 11 Sep 2024 15:38:17 -0700 [thread overview]
Message-ID: <20240911153817.0c150bc6@kernel.org> (raw)
In-Reply-To: <20240911153633.7a01a6c7@kernel.org>
On Wed, 11 Sep 2024 15:36:33 -0700 Jakub Kicinski wrote:
> > What's the deadline for these? Do you need the fixes tomorrow or can it
> > wait a week or two?
>
> It can wait, half of them are old anyway
Oh, that's because they are in staging :) I missed that.
But anyway, I don't think that a harmless, single compiler,
W=1 warning is a blocker.
next prev parent reply other threads:[~2024-09-11 22:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 8:41 pull-request: wireless-next-2024-09-11 Kalle Valo
2024-09-11 20:45 ` Jakub Kicinski
2024-09-11 22:29 ` Kalle Valo
2024-09-11 22:36 ` Jakub Kicinski
2024-09-11 22:38 ` Jakub Kicinski [this message]
2024-09-12 2:33 ` Ping-Ke Shih
2024-09-12 6:28 ` Kalle Valo
2024-09-12 6:33 ` Ping-Ke Shih
2024-09-11 22:30 ` patchwork-bot+netdevbpf
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=20240911153817.0c150bc6@kernel.org \
--to=kuba@kernel.org \
--cc=kvalo@kernel.org \
--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).