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-next-2022-07-13
Date: Wed, 13 Jul 2022 11:53:49 -0700 [thread overview]
Message-ID: <20220713115349.1703bb92@kernel.org> (raw)
In-Reply-To: <20220713071932.20538-1-johannes@sipsolutions.net>
On Wed, 13 Jul 2022 09:19:31 +0200 Johannes Berg wrote:
> Hi,
>
> And another one, for next! This one's big, due to the first
> parts of multi-link operation (MLO) support - though that's
> not nearly done yet (have probably about as many patches as
> here already in the pipeline again).
>
> Please pull and let me know if there's any problem.
Dave already pulled (I haven't seen the pw-bot reply, let's see whether
it will reply if I just flip the state back to "Under review" now).
Please take a gander at the new warnings in:
https://patchwork.kernel.org/project/netdevbpf/patch/20220713071932.20538-1-johannes@sipsolutions.net/
to make sure they are expected.
next prev parent reply other threads:[~2022-07-13 18:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 7:19 pull-request: wireless-next-2022-07-13 Johannes Berg
2022-07-13 18:53 ` Jakub Kicinski [this message]
2022-07-13 19:12 ` Johannes Berg
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=20220713115349.1703bb92@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).