From: netdev-bot+sashiko@kernel.org
To: willemdebruijn.kernel@gmail.com
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
edumazet@google.com, pabeni@redhat.com, horms@kernel.org,
andrew+netdev@lunn.ch, willemb@google.com
Subject: Re: [PATCH net-next v8 4/6] selftests: drv-net: refactor so_txtime errqueue handling
Date: Fri, 04 Sep 2026 00:19:44 +0000 [thread overview]
Message-ID: <178848118486.4131868.16349357312570798232@kernel.org> (raw)
In-Reply-To: <20260902181747.2483351-5-willemdebruijn.kernel@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential
issue(s) to consider:
Critical: 0 · High: 0 · Medium: 0 · Low: 1
- [Low] Commit message hygiene: the per-revision changelog block of
commit "selftests: drv-net: refactor so_txtime errqueue handling"…
--
selftests: drv-net: refactor so_txtime errqueue handling
This patch splits do_recv_errqueue_timeout() in
tools/testing/selftests/drivers/net/so_txtime.c into a dispatcher
do_recv_errqueue() plus a new helper do_recv_errqueue_txtime() that keeps the
SO_EE_ORIGIN_TXTIME specific handling. It is preparation for handling
SO_EE_ORIGIN_TIMESTAMPING messages in the following patch, with no functional
change intended.
The only comment below concerns the recorded commit message, so the diff hunks
are omitted.
> Signed-off-by: Willem de Bruijn <willemb@google.com>
>
> --
>
> Changes
> v3 -> v4
> - rename func to do_recv_errqueue_txtime
[Severity: Low]
This isn't a code bug, but should the per-revision changelog be separated by
a three-dash line instead of "--"?
git mailinfo only truncates the message at a line of exactly three dashes or
at an explicit scissors marker, so a "--" line is kept as ordinary body text.
The recorded commit for d88dea26ea55958d0982df4811107d0743ccf08d ends with:
Signed-off-by: Willem de Bruijn <willemb@google.com>
--
Changes
v3 -> v4
- rename func to do_recv_errqueue_txtime
That leaves the changelog permanently in the git history, and it sits after
the Signed-off-by trailer, so the trailer block is no longer the last section
of the message.
Could this be resent with "---" before the changelog block, or with the block
dropped?
--
Sashiko AI review · https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20260902181747.2483351-1-willemdebruijn.kernel%40gmail.com
next prev parent reply other threads:[~2026-09-04 0:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 18:17 [PATCH net-next v8 0/6] hardware pacing offload Willem de Bruijn
2026-09-02 18:17 ` [PATCH net-next v8 1/6] net: rtnetlink: add pacing_offload_horizon attribute to net_device Willem de Bruijn
2026-09-04 0:19 ` netdev-bot+sashiko
2026-09-04 23:01 ` Jakub Kicinski
2026-09-06 2:22 ` Willem de Bruijn
2026-09-07 23:12 ` Jakub Kicinski
2026-09-08 0:50 ` Willem de Bruijn
2026-09-08 20:48 ` Willem de Bruijn
2026-09-08 21:48 ` Jakub Kicinski
2026-09-08 22:39 ` Willem de Bruijn
2026-09-08 23:34 ` Jakub Kicinski
2026-09-09 15:47 ` Willem de Bruijn
2026-09-09 18:13 ` Jakub Kicinski
2026-09-02 18:17 ` [PATCH net-next v8 2/6] net_sched: sch_fq: clear past skb->tstamp if offloading pacing Willem de Bruijn
2026-09-02 18:17 ` [PATCH net-next v8 3/6] idpf: support pacing offload Willem de Bruijn
2026-09-04 0:19 ` netdev-bot+sashiko
2026-09-04 15:22 ` Willem de Bruijn
2026-09-07 9:30 ` Loktionov, Aleksandr
2026-09-10 17:14 ` Willem de Bruijn
2026-09-02 18:17 ` [PATCH net-next v8 4/6] selftests: drv-net: refactor so_txtime errqueue handling Willem de Bruijn
2026-09-04 0:19 ` netdev-bot+sashiko [this message]
2026-09-02 18:17 ` [PATCH net-next v8 5/6] selftests: drv-net: in so_txtime tell apart sw from hw pacing Willem de Bruijn
2026-09-04 0:19 ` netdev-bot+sashiko
2026-09-02 18:17 ` [PATCH net-next v8 6/6] selftests: drv-net: extend so_txtime with hw offload Willem de Bruijn
2026-09-04 0:19 ` netdev-bot+sashiko
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=178848118486.4131868.16349357312570798232@kernel.org \
--to=netdev-bot+sashiko@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.com \
--cc=willemdebruijn.kernel@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 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.