From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com
Subject: Re: [PATCH net-next v2 0/2] ethtool: netlink: handle SET intro/outro in the common code
Date: Fri, 27 Jan 2023 12:40:17 +0000 [thread overview]
Message-ID: <167482321701.11366.17179685426572942590.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230125230519.1069676-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Wed, 25 Jan 2023 15:05:17 -0800 you wrote:
> Factor out the boilerplate code from SET handlers to common code.
>
> I volunteered to refactor the extack in GET in a conversation
> with Vladimir but I gave up.
>
> The handling of failures during dump in GET handlers is a bit
> unclear to me. Some code uses presence of info as indication
> of dump and tries to avoid reporting errors altogether
> (including extack messages).
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] ethtool: netlink: handle SET intro/outro in the common code
https://git.kernel.org/netdev/net-next/c/99132b6eb792
- [net-next,v2,2/2] ethtool: netlink: convert commands to common SET
https://git.kernel.org/netdev/net-next/c/04007961bfaf
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-01-27 12:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 23:05 [PATCH net-next v2 0/2] ethtool: netlink: handle SET intro/outro in the common code Jakub Kicinski
2023-01-25 23:05 ` [PATCH net-next v2 1/2] " Jakub Kicinski
2023-01-25 23:05 ` [PATCH net-next v2 2/2] ethtool: netlink: convert commands to common SET Jakub Kicinski
2023-01-27 12: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=167482321701.11366.17179685426572942590.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--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 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.