From: patchwork-bot+netdevbpf@kernel.org
To: Johannes Berg <johannes@sipsolutions.net>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH net-next v4 0/3] net: extend drop reasons
Date: Fri, 21 Apr 2023 03:40:19 +0000 [thread overview]
Message-ID: <168204841995.12253.8809097990085515051.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230419125254.20789-1-johannes@sipsolutions.net>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 19 Apr 2023 14:52:51 +0200 you wrote:
> Hi,
>
> Here's v4 of the extended drop reasons, with fixes to kernel-doc
> and checkpatch.
>
> johannes
Here is the summary with links:
- [net-next,v4,1/3] net: move dropreason.h to dropreason-core.h
https://git.kernel.org/netdev/net-next/c/5b8285cca6fe
- [net-next,v4,2/3] net: extend drop reasons for multiple subsystems
https://git.kernel.org/netdev/net-next/c/071c0fc6fb91
- [net-next,v4,3/3] mac80211: use the new drop reasons infrastructure
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-04-21 3:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 12:52 [PATCH net-next v4 0/3] net: extend drop reasons Johannes Berg
2023-04-19 12:52 ` [PATCH net-next v4 1/3] net: move dropreason.h to dropreason-core.h Johannes Berg
2023-04-19 12:52 ` [PATCH net-next v4 2/3] net: extend drop reasons for multiple subsystems Johannes Berg
2023-04-20 15:20 ` Simon Horman
2023-04-19 12:52 ` [PATCH net-next v4 3/3] mac80211: use the new drop reasons infrastructure Johannes Berg
2023-04-20 15:21 ` Simon Horman
2023-04-21 3:40 ` 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=168204841995.12253.8809097990085515051.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.