From: patchwork-bot+netdevbpf@kernel.org
To: Simon Horman <horms@kernel.org>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, johannes@sipsolutions.net,
willemdebruijn.kernel@gmail.com, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
willemb@google.com
Subject: Re: [PATCH net v2 0/2] MAINTAINERS: Networking file coverage updates
Date: Thu, 10 Oct 2024 16:40:28 +0000 [thread overview]
Message-ID: <172857842850.2091174.8907404119655762226.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241009-maint-net-hdrs-v2-0-f2c86e7309c8@kernel.org>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 09 Oct 2024 09:47:21 +0100 you wrote:
> Hi,
>
> The aim of this proposal is to make the handling of some files,
> related to Networking and Wireless, more consistently. It does so by:
>
> 1. Adding some more headers to the UDP section, making it consistent
> with the TCP section.
>
> [...]
Here is the summary with links:
- [net,v2,1/2] MAINTAINERS: consistently exclude wireless files from NETWORKING [GENERAL]
https://git.kernel.org/netdev/net/c/9937aae39bc0
- [net,v2,2/2] MAINTAINERS: Add headers and mailing list to UDP section
https://git.kernel.org/netdev/net/c/5404b5a2fea9
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:[~2024-10-10 16:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 8:47 Simon Horman
2024-10-09 8:47 ` [PATCH net v2 1/2] MAINTAINERS: consistently exclude wireless files from NETWORKING [GENERAL] Simon Horman
2024-10-09 8:47 ` [PATCH net v2 2/2] MAINTAINERS: Add headers and mailing list to UDP section Simon Horman
2024-10-10 16: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=172857842850.2091174.8907404119655762226.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.com \
--cc=willemdebruijn.kernel@gmail.com \
/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
all inboxes | Powered by JetHome®