From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Xin Zhao <jackzxcui1989@163.com>,
willemdebruijn.kernel@gmail.com, edumazet@google.com,
ferenc@fejes.dev
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v10 2/2] net: af_packet: Use hrtimer to do the retire operation
Date: Mon, 01 Sep 2025 09:35:31 -0400 [thread overview]
Message-ID: <willemdebruijn.kernel.38c4c9c6a77df@gmail.com> (raw)
In-Reply-To: <20250901022744.1794421-1-jackzxcui1989@163.com>
Xin Zhao wrote:
> On Sun, 2025-08-31 at 21:21 -0400, Willem wrote:
>
> > > - p1->retire_blk_tov = prb_calc_retire_blk_tmo(po,
> > > - req_u->req3.tp_block_size);
> > > - p1->tov_in_jiffies = msecs_to_jiffies(p1->retire_blk_tov);
> > > + p1->interval_ktime = ms_to_ktime(prb_calc_retire_blk_tmo(po,
> > > + req_u->req3.tp_block_size));
> >
> > req_u is not aligned with the line above.
>
> I have some questions regarding the alignment here. According to the alignment requirements,
> req_u should be aligned below the po variable. However, if it is aligned below po, the line
> will become very long, which may affect readability. In this special case, can I align it to
> prb_calc_retire_blk_tmo instead, or should I continue to align it to the po variable?
The (minor) issue here is with the second req_u. Which is one space
off from the argument above. See checkpath.
In general, the line length and break rules are documented in the
kernel coding style page, which checkpatch follows.
>
> What should I do next?
> Should I change the alignment, and resend PATCH with the reviewed information of version 10?
I did not think this one space was worth resending, so I added my
Reviewed-by. Others may disagree, but so far no other opinions.
next prev parent reply other threads:[~2025-09-01 13:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-01 2:27 [PATCH net-next v10 2/2] net: af_packet: Use hrtimer to do the retire operation Xin Zhao
2025-09-01 13:35 ` Willem de Bruijn [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-09-05 14:47 Xin Zhao
2025-09-05 16:16 ` Willem de Bruijn
2025-09-05 4:00 Xin Zhao
2025-09-05 6:03 ` Jason Xing
2025-09-05 6:45 ` Jason Xing
2025-09-05 16:16 ` Willem de Bruijn
2025-09-06 0:14 ` Jason Xing
2025-09-06 15:25 ` Willem de Bruijn
2025-09-06 15:53 ` Jason Xing
2025-09-04 14:59 Xin Zhao
2025-09-05 0:09 ` Jason Xing
2025-09-03 17:07 Xin Zhao
2025-09-04 3:26 ` Jason Xing
2025-09-03 16:17 Xin Zhao
2025-09-04 2:50 ` Jason Xing
2025-09-01 14:16 Xin Zhao
2025-08-31 10:08 [PATCH net-next v10 0/2] net: af_packet: optimize " Xin Zhao
2025-08-31 10:08 ` [PATCH net-next v10 2/2] net: af_packet: Use hrtimer to do the " Xin Zhao
2025-09-01 1:21 ` Willem de Bruijn
2025-09-02 15:43 ` Jason Xing
2025-09-02 16:42 ` Jason Xing
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=willemdebruijn.kernel.38c4c9c6a77df@gmail.com \
--to=willemdebruijn.kernel@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ferenc@fejes.dev \
--cc=horms@kernel.org \
--cc=jackzxcui1989@163.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.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.