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: [GIT PULL] wireless-next-2026-09-21
Date: Tue, 22 Sep 2026 01:20:23 +0000	[thread overview]
Message-ID: <179004002314.3321385.8021134198835794287.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260921121635.195723-3-johannes@sipsolutions.net>

Hello:

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

On Mon, 21 Sep 2026 14:13:46 +0200 you wrote:
> Hi,
> 
> Some more changes - mostly not very interesting I guess.
> I haven't received most driver updates yet.
> 
> Note there are some merge conflicts - most are reasonably
> easy but the bigger net/mac80211/tx.c one is a bit annoying,
> but it's "take the wireless-next version". I've pushed an
> example resolution to the 'merge-2026-09-21' branch in my
> (wireless-next) tree.
> (I had fixed an issue in wireless, but also did some bigger
> refactoring/cleanup in wireless-next that fixed the same
> issue as well, just differently.)
> 
> [...]

Here is the summary with links:
  - [GIT,PULL] wireless-next-2026-09-21
    https://git.kernel.org/netdev/net-next/c/10cfa109c880

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



      reply	other threads:[~2026-09-22  1:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-21 12:13 [GIT PULL] wireless-next-2026-09-21 Johannes Berg
2026-09-22  1:20 ` 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=179004002314.3321385.8021134198835794287.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.