From: patchwork-bot+netdevbpf@kernel.org
To: Hangbin Liu <liuhangbin@gmail.com>
Cc: netdev@vger.kernel.org, jhs@mojatatu.com,
xiyou.wangcong@gmail.com, jiri@resnulli.us, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
dsahern@kernel.org
Subject: Re: [PATCH iproute2-next 1/2] libnetlink: add offset for nl_dump_ext_ack_done
Date: Wed, 28 Sep 2022 03:30:15 +0000 [thread overview]
Message-ID: <166433581572.10603.5778674738651623494.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220927102107.191852-1-liuhangbin@gmail.com>
Hello:
This patch was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:
On Tue, 27 Sep 2022 18:21:06 +0800 you wrote:
> There is no rule to have an error code after NLMSG_DONE msg. The only reason
> we has this offset is that kernel function netlink_dump_done() has an error
> code followed by the netlink message header.
>
> Making nl_dump_ext_ack_done() has an offset parameter. So we can adjust
> this for NLMSG_DONE message without error code.
>
> [...]
Here is the summary with links:
- [iproute2-next,1/2] libnetlink: add offset for nl_dump_ext_ack_done
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=80059fa5c5ed
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-09-28 3:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 10:17 [PATCH net-next] sched: add extack for tfilter_notify Hangbin Liu
2022-09-27 10:21 ` [PATCH iproute2-next 1/2] libnetlink: add offset for nl_dump_ext_ack_done Hangbin Liu
2022-09-28 3:30 ` patchwork-bot+netdevbpf [this message]
2022-09-27 10:21 ` [PATCH iproute2-next 2/2] tc/tc_monitor: print netlink extack message Hangbin Liu
2022-09-28 3:30 ` [PATCH net-next] sched: add extack for tfilter_notify patchwork-bot+netdevbpf
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=166433581572.10603.5778674738651623494.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=xiyou.wangcong@gmail.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).