From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, andrew@lunn.ch,
mkubecek@suse.cz
Subject: Re: [PATCH net-next 0/3] ethtool: fec: ioctl kdoc touch ups
Date: Fri, 26 Mar 2021 23:00:12 +0000 [thread overview]
Message-ID: <161679961252.14639.9738109467037178288.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210326202223.302085-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Fri, 26 Mar 2021 13:22:20 -0700 you wrote:
> A few touch ups from v1 review.
>
> Jakub Kicinski (3):
> ethtool: fec: add note about reuse of reserved
> ethtool: fec: fix FEC_NONE check
> ethtool: document the enum values not defines
>
> [...]
Here is the summary with links:
- [net-next,1/3] ethtool: fec: add note about reuse of reserved
https://git.kernel.org/netdev/net-next/c/ad1cd7856d87
- [net-next,2/3] ethtool: fec: fix FEC_NONE check
https://git.kernel.org/netdev/net-next/c/cf2cc0bf4fde
- [net-next,3/3] ethtool: document the enum values not defines
https://git.kernel.org/netdev/net-next/c/d04feecaf154
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-03-26 23:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 20:22 [PATCH net-next 0/3] ethtool: fec: ioctl kdoc touch ups Jakub Kicinski
2021-03-26 20:22 ` [PATCH net-next 1/3] ethtool: fec: add note about reuse of reserved Jakub Kicinski
2021-03-26 20:22 ` [PATCH net-next 2/3] ethtool: fec: fix FEC_NONE check Jakub Kicinski
2021-03-26 20:22 ` [PATCH net-next 3/3] ethtool: document the enum values not defines Jakub Kicinski
2021-03-26 23:00 ` 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=161679961252.14639.9738109467037178288.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=mkubecek@suse.cz \
--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.