From: patchwork-bot+netdevbpf@kernel.org
To: Nikolay Aleksandrov <razor@blackwall.org>
Cc: netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
roopa@nvidia.com, kuba@kernel.org
Subject: Re: [Bridge] [PATCH net-next] net: bridge: fill in MODULE_DESCRIPTION()
Date: Fri, 27 Oct 2023 10:20:24 +0000 [thread overview]
Message-ID: <169840202448.15376.8674341343569691359.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231027100549.1695865-1-razor@blackwall.org>
Hello:
This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 27 Oct 2023 13:05:49 +0300 you wrote:
> Fill in bridge's module description.
>
> Suggested-by: Jakub Kicinski <kuba@kernel.org>
> Signed-off-by: Nikolay Aleksandrov <razor@blackwall.org>
> ---
> net/bridge/br.c | 1 +
> 1 file changed, 1 insertion(+)
Here is the summary with links:
- [net-next] net: bridge: fill in MODULE_DESCRIPTION()
https://git.kernel.org/netdev/net-next/c/6808918343a8
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+netdevbpf@kernel.org
To: Nikolay Aleksandrov <razor@blackwall.org>
Cc: netdev@vger.kernel.org, kuba@kernel.org,
bridge@lists.linux-foundation.org, roopa@nvidia.com
Subject: Re: [PATCH net-next] net: bridge: fill in MODULE_DESCRIPTION()
Date: Fri, 27 Oct 2023 10:20:24 +0000 [thread overview]
Message-ID: <169840202448.15376.8674341343569691359.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231027100549.1695865-1-razor@blackwall.org>
Hello:
This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 27 Oct 2023 13:05:49 +0300 you wrote:
> Fill in bridge's module description.
>
> Suggested-by: Jakub Kicinski <kuba@kernel.org>
> Signed-off-by: Nikolay Aleksandrov <razor@blackwall.org>
> ---
> net/bridge/br.c | 1 +
> 1 file changed, 1 insertion(+)
Here is the summary with links:
- [net-next] net: bridge: fill in MODULE_DESCRIPTION()
https://git.kernel.org/netdev/net-next/c/6808918343a8
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-10-27 10:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 19:00 [PATCH net-next 0/4] net: fill in 18 MODULE_DESCRIPTION()s Jakub Kicinski
2023-10-26 19:00 ` [PATCH net-next 1/4] net: fill in MODULE_DESCRIPTION()s in kuba@'s modules Jakub Kicinski
2023-10-27 6:54 ` Kalle Valo
2023-10-27 14:15 ` Jonathan Bither
2023-10-27 14:28 ` Jakub Kicinski
2023-10-26 19:00 ` [PATCH net-next 2/4] net: fill in MODULE_DESCRIPTION()s under net/core Jakub Kicinski
2023-10-27 4:52 ` Oleksij Rempel
2023-10-26 19:01 ` [PATCH net-next 3/4] net: fill in MODULE_DESCRIPTION()s under net/802* Jakub Kicinski
2023-10-26 19:11 ` Greg KH
2023-10-26 19:01 ` [PATCH net-next 4/4] net: fill in MODULE_DESCRIPTION()s under drivers/net/ Jakub Kicinski
2023-10-26 20:00 ` Willem de Bruijn
2023-10-26 22:46 ` Jamal Hadi Salim
2023-10-27 6:35 ` Arnd Bergmann
2023-10-27 6:50 ` Jason Wang
2023-10-27 7:37 ` Taehee Yoo
2023-10-27 10:05 ` [Bridge] [PATCH net-next] net: bridge: fill in MODULE_DESCRIPTION() Nikolay Aleksandrov
2023-10-27 10:05 ` Nikolay Aleksandrov
2023-10-27 10:20 ` patchwork-bot+netdevbpf [this message]
2023-10-27 10:20 ` patchwork-bot+netdevbpf
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=169840202448.15376.8674341343569691359.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bridge@lists.linux-foundation.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=razor@blackwall.org \
--cc=roopa@nvidia.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 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.