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, dsahern@gmail.com, mkubecek@suse.cz
Subject: Re: [PATCH net-next 0/2] net: support extack in dump and simplify ethtool uAPI
Date: Mon, 12 Jun 2023 10:40:21 +0000 [thread overview]
Message-ID: <168656642135.24269.3640135425703841273.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230609215331.1606292-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 9 Jun 2023 14:53:29 -0700 you wrote:
> Ethtool currently requires header nest to be always present even if
> it doesn't have to carry any attr for a given request. This inflicts
> unnecessary pain on the users.
>
> What makes it worse is that extack was not working in dump's ->start()
> callback. Address both of those issues.
>
> [...]
Here is the summary with links:
- [net-next,1/2] netlink: support extack in dump ->start()
https://git.kernel.org/netdev/net-next/c/5ab8c41cef30
- [net-next,2/2] net: ethtool: don't require empty header nests
https://git.kernel.org/netdev/net-next/c/500e1340d1d2
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-06-12 10:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 21:53 [PATCH net-next 0/2] net: support extack in dump and simplify ethtool uAPI Jakub Kicinski
2023-06-09 21:53 ` [PATCH net-next 1/2] netlink: support extack in dump ->start() Jakub Kicinski
2023-06-09 21:53 ` [PATCH net-next 2/2] net: ethtool: don't require empty header nests Jakub Kicinski
2023-06-12 10: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=168656642135.24269.3640135425703841273.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=mkubecek@suse.cz \
--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).