From: patchwork-bot+netdevbpf@kernel.org
To: Antoine Tenart <atenart@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
juri.lelli@redhat.com, mhocko@suse.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/3] net: introduce a function to check if a netdev name is in use
Date: Fri, 08 Oct 2021 16:30:09 +0000 [thread overview]
Message-ID: <163371060917.30754.1813039576071539612.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211007161652.374597-1-atenart@kernel.org>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Thu, 7 Oct 2021 18:16:49 +0200 you wrote:
> Hello,
>
> This was initially part of an RFC series[1] but has value on its own;
> hence the standalone report. (It will also help in not having a series
> too large).
>
> From patch 1:
>
> [...]
Here is the summary with links:
- [net-next,1/3] net: introduce a function to check if a netdev name is in use
https://git.kernel.org/netdev/net-next/c/75ea27d0d622
- [net-next,2/3] bonding: use the correct function to check for netdev name collision
https://git.kernel.org/netdev/net-next/c/caa9b35fadff
- [net-next,3/3] ppp: use the correct function to check if a netdev name is in use
https://git.kernel.org/netdev/net-next/c/d03eb9787d3a
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:[~2021-10-08 16:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-07 16:16 [PATCH net-next 0/3] net: introduce a function to check if a netdev name is in use Antoine Tenart
2021-10-07 16:16 ` [PATCH net-next 1/3] " Antoine Tenart
2021-10-07 16:16 ` [PATCH net-next 2/3] bonding: use the correct function to check for netdev name collision Antoine Tenart
2021-10-07 16:16 ` [PATCH net-next 3/3] ppp: use the correct function to check if a netdev name is in use Antoine Tenart
2021-10-08 16:30 ` 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=163371060917.30754.1813039576071539612.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=atenart@kernel.org \
--cc=davem@davemloft.net \
--cc=juri.lelli@redhat.com \
--cc=kuba@kernel.org \
--cc=mhocko@suse.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).