All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Johannes Berg <johannes@sipsolutions.net>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: pull-request: wireless-next-2023-03-30
Date: Fri, 31 Mar 2023 07:10:31 +0000	[thread overview]
Message-ID: <168024663114.20376.13843160460132792277.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230330205612.921134-1-johannes@sipsolutions.net>

Hello:

This pull request was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Thu, 30 Mar 2023 22:56:11 +0200 you wrote:
> Hi,
> 
> Here's new content for -next, this time with a bunch
> of the promised iwlwifi work, but also lots of changes
> in other drivers and some new stack features.
> 
> I also mention it in the tag, but Kalle moved all the
> plain C files out of drivers/net/wireless/ into dirs,
> just FYI.
> 
> [...]

Here is the summary with links:
  - pull-request: wireless-next-2023-03-30
    https://git.kernel.org/netdev/net-next/c/ce7928f7cf98

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2023-03-31  7:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30 20:56 pull-request: wireless-next-2023-03-30 Johannes Berg
2023-03-31  7:06 ` Jakub Kicinski
2023-04-03 22:45   ` Richard Cochran
2023-04-13  3:33     ` Richard Cochran
2023-04-18 13:35       ` Greenman, Gregory
2023-04-20  3:43         ` Richard Cochran
2023-04-23 13:33           ` Stern, Avraham
2023-04-24 22:04             ` Richard Cochran
2023-04-25  1:29               ` Richard Cochran
2023-04-25  7:03                 ` Stern, Avraham
2023-04-26  2:43                   ` Richard Cochran
2023-04-26 14:04                     ` Richard Cochran
2023-05-07 16:32                     ` Stern, Avraham
2023-03-31  7:10 ` patchwork-bot+netdevbpf [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=168024663114.20376.13843160460132792277.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.