netdev.vger.kernel.org archive mirror
 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-2023-10-24
Date: Tue, 24 Oct 2023 20:20:24 +0000	[thread overview]
Message-ID: <169817882433.2839.2840092877928784369.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231024103540.19198-2-johannes@sipsolutions.net>

Hello:

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

On Tue, 24 Oct 2023 12:35:41 +0200 you wrote:
> Hi,
> 
> We have a couple of last-minute fixes for some issues.
> 
> Note that this introduces a merge conflict with -next,
> which Stephen reported and (correctly) resolved here:
> https://lore.kernel.org/linux-wireless/20231024112424.7de86457@canb.auug.org.au/
> Basically just context - use the ieee80211_is_protected_dual_of_public_action()
> check from this pull request, and the return code
> RX_DROP_U_UNPROT_UNICAST_PUB_ACTION from -next.
> 
> [...]

Here is the summary with links:
  - pull-request: wireless-2023-10-24
    https://git.kernel.org/netdev/net/c/00d67093e4f1

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



  reply	other threads:[~2023-10-24 20:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-24 10:35 pull-request: wireless-2023-10-24 Johannes Berg
2023-10-24 20:20 ` patchwork-bot+netdevbpf [this message]
2023-10-24 20:25   ` Johannes Berg
2023-10-24 20:52     ` Jakub Kicinski
2023-10-24 20:54       ` Johannes Berg
2023-10-24 21:01         ` Jakub Kicinski
2023-10-24 21:03           ` 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=169817882433.2839.2840092877928784369.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 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).