From: patchwork-bot+netdevbpf@kernel•org
To: Jesse Brandeburg <jesse.brandeburg@intel•com>
Cc: kuba@kernel•org, davem@davemloft•net, pabeni@redhat•com,
netdev@vger•kernel.org, intel-wired-lan@lists•osuosl.org,
edumazet@google•com
Subject: Re: [PATCH net-next v1 0/2] net/core: commmon prints for promisc
Date: Thu, 16 Feb 2023 09:40:17 +0000 [thread overview]
Message-ID: <167654041768.15687.3979753210870532003.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230214210117.23123-1-jesse.brandeburg@intel.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@redhat•com>:
On Tue, 14 Feb 2023 13:01:15 -0800 you wrote:
> Add a print to the kernel log for allmulticast entry and exit, and
> standardize the print for entry and exit of promiscuous mode.
>
> These prints are useful to both user and developer and should have the
> triggering driver/bus/device info that netdev_info (optionally) gives.
>
> Jesse Brandeburg (2):
> net/core: print message for allmulticast
> net/core: refactor promiscuous mode message
>
> [...]
Here is the summary with links:
- [net-next,v1,1/2] net/core: print message for allmulticast
https://git.kernel.org/netdev/net-next/c/802dcbd6f30f
- [net-next,v1,2/2] net/core: refactor promiscuous mode message
https://git.kernel.org/netdev/net-next/c/3ba0bf47edf9
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-02-16 9:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 21:01 [PATCH net-next v1 0/2] net/core: commmon prints for promisc Jesse Brandeburg
2023-02-14 21:01 ` [PATCH net-next v1 1/2] net/core: print message for allmulticast Jesse Brandeburg
2023-02-14 21:01 ` [PATCH net-next v1 2/2] net/core: refactor promiscuous mode message Jesse Brandeburg
2023-02-16 9:10 ` Paolo Abeni
2023-02-16 9: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=167654041768.15687.3979753210870532003.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=intel-wired-lan@lists$(echo .)osuosl.org \
--cc=jesse.brandeburg@intel$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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