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: mac80211 2021-01-18.2
Date: Mon, 18 Jan 2021 22:50:09 +0000	[thread overview]
Message-ID: <161101020906.2232.13826999223880000897.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210118204750.7243-1-johannes@sipsolutions.net>

Hello:

This pull request was applied to netdev/net.git (refs/heads/master):

On Mon, 18 Jan 2021 21:47:49 +0100 you wrote:
> Hi,
> 
> New try, dropped the 160 MHz CSA patch for now that has the sparse
> issue since people are waiting for the kernel-doc fixes.
> 
> Please pull and let me know if there's any problem.
> 
> [...]

Here is the summary with links:
  - pull-request: mac80211 2021-01-18.2
    https://git.kernel.org/netdev/net/c/bde2c0af6141

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



  reply	other threads:[~2021-01-18 22:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-18 20:47 pull-request: mac80211 2021-01-18.2 Johannes Berg
2021-01-18 22:50 ` patchwork-bot+netdevbpf [this message]
2021-01-20 17:59   ` Johannes Berg
2021-01-20 20:37     ` Jakub Kicinski
2021-01-20 20:39       ` Johannes Berg
2021-01-23 21:31 ` Hans de Goede
2021-01-23 22:15   ` Johannes Berg
2021-01-24  9:12     ` Peer, Ilan
2021-01-24 10:54       ` Hans de Goede
2021-01-24 13:03         ` Peer, Ilan
2021-01-25  9:47         ` Johannes Berg
2021-01-25 11:18           ` Hans de Goede
2021-01-25 12:40             ` Johannes Berg
2021-01-25 12:59               ` Hans de Goede
2021-01-25 13: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=161101020906.2232.13826999223880000897.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.