netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakob Koschel <jakobkoschel@gmail.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: Ariel Elior <aelior@marvell.com>,
	Sudarsana Kalluru <skalluru@marvell.com>,
	Manish Chopra <manishc@marvell.com>,
	"David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Mike Rapoport <rppt@kernel.org>,
	Brian Johannesmeyer <bjohannesmeyer@gmail.com>,
	Cristiano Giuffrida <c.giuffrida@vu.nl>,
	"Bos, H.J." <h.j.bos@vu.nl>
Subject: Re: [PATCH] bnx2x: replace usage of found with dedicated list iterator variable
Date: Sun, 27 Mar 2022 23:32:17 +0200	[thread overview]
Message-ID: <A2882749-A512-447C-B28F-37BEC287A614@gmail.com> (raw)
In-Reply-To: <7393b673c626fd75f2b4f8509faa5459254fb87c.camel@redhat.com>

Hello,

> On 24. Mar 2022, at 11:46, Paolo Abeni <pabeni@redhat.com> wrote:
> 
> Hello,
> 
> On Thu, 2022-03-24 at 08:08 +0100, Jakob Koschel wrote:
>> To move the list iterator variable into the list_for_each_entry_*()
>> macro in the future it should be avoided to use the list iterator
>> variable after the loop body.
>> 
>> To *never* use the list iterator variable after the loop it was
>> concluded to use a separate iterator variable instead of a
>> found boolean [1].
>> 
>> This removes the need to use a found variable and simply checking if
>> the variable was set, can determine if the break/goto was hit.
>> 
>> Link: https://lore.kernel.org/all/CAHk-=wgRr_D8CB-D9Kg-c=EHreAsk5SqXPwr9Y7k9sA6cWXJ6w@mail.gmail.com/
>> Signed-off-by: Jakob Koschel <jakobkoschel@gmail.com>
> 
> This looks like a purely net-next change, and we are in the merge
> window: net-next is closed for the time being. Could you please re-post
> after net-next re-open?

Thanks for letting me know, I'll re-post after net-next is reopened.

> 
> Additionally, I suggest you to bundle the net-next patches in a single
> series, namely:

Are you saying having a single patchset for all /net and /drivers/net
related changes? This would also simplify a lot on my end.


> 
> bnx2x: replace usage of found with dedicated list iterator variable 
> octeontx2-pf: replace usage of found with dedicated list iterator variable 
> sctp: replace usage of found with dedicated list iterator variable 
> taprio: replace usage of found with dedicated list iterator variable 
> 
> that will simplify the processing, thanks!
> 
> Paolo

Thanks,
Jakob


      reply	other threads:[~2022-03-27 21:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-24  7:08 [PATCH] bnx2x: replace usage of found with dedicated list iterator variable Jakob Koschel
2022-03-24 10:46 ` Paolo Abeni
2022-03-27 21:32   ` Jakob Koschel [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=A2882749-A512-447C-B28F-37BEC287A614@gmail.com \
    --to=jakobkoschel@gmail.com \
    --cc=aelior@marvell.com \
    --cc=bjohannesmeyer@gmail.com \
    --cc=c.giuffrida@vu.nl \
    --cc=davem@davemloft.net \
    --cc=h.j.bos@vu.nl \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manishc@marvell.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rppt@kernel.org \
    --cc=skalluru@marvell.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).