From: patchwork-bot+netdevbpf@kernel.org
To: Rocco Yue <rocco.yue@mediatek.com>
Cc: dsahern@kernel.org, davem@davemloft.net, kuba@kernel.org,
yoshfuji@linux-ipv6.org, matthias.bgg@gmail.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, rocco.yue@gmail.com,
chao.song@mediatek.com, zhuoliang.zhang@mediatek.com
Subject: Re: [PATCH net-next] net: add extack arg for link ops
Date: Wed, 04 Aug 2021 09:10:05 +0000 [thread overview]
Message-ID: <162806820573.32022.14403323895648321150.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210803120250.32642-1-rocco.yue@mediatek.com>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Tue, 3 Aug 2021 20:02:50 +0800 you wrote:
> Pass extack arg to validate_linkmsg and validate_link_af callbacks.
> If a netlink attribute has a reject_message, use the extended ack
> mechanism to carry the message back to user space.
>
> Signed-off-by: Rocco Yue <rocco.yue@mediatek.com>
> ---
> include/net/rtnetlink.h | 3 ++-
> net/core/rtnetlink.c | 9 +++++----
> net/ipv4/devinet.c | 5 +++--
> net/ipv6/addrconf.c | 5 +++--
> 4 files changed, 13 insertions(+), 9 deletions(-)
Here is the summary with links:
- [net-next] net: add extack arg for link ops
https://git.kernel.org/netdev/net-next/c/8679c31e0284
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-08-04 9:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 12:02 [PATCH net-next] net: add extack arg for link ops Rocco Yue
2021-08-03 14:32 ` David Ahern
2021-08-04 9:10 ` 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=162806820573.32022.14403323895648321150.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=chao.song@mediatek.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=rocco.yue@gmail.com \
--cc=rocco.yue@mediatek.com \
--cc=yoshfuji@linux-ipv6.org \
--cc=zhuoliang.zhang@mediatek.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).