From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Stefan Wahren <stefan.wahren@i2se.com>,
devel@driverdev.osuosl.org, Arnd Bergmann <arnd@arndb.de>,
Marcelo Diop-Gonzalez <marcgonzalez@google.com>,
kernel-janitors@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
linux-rpi-kernel@lists.infradead.org,
Jamal Shareef <jamal.k.shareef@gmail.com>,
Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
Subject: Re: [PATCH] staging: vchiq: Fix list_for_each exit tests
Date: Thu, 01 Oct 2020 08:56:50 +0000 [thread overview]
Message-ID: <20201001085650.GA1832570@kroah.com> (raw)
In-Reply-To: <20200928091103.GC377727@mwanda>
On Mon, Sep 28, 2020 at 12:11:03PM +0300, Dan Carpenter wrote:
> This code code here used to be list_for_each() and after the loop then
> the "entry" pointer was non-NULL if we found the correct entry or NULL
> if we couldn't find it. Then we changed the code to use list_for_each_entry()
> and so now the "entry" pointer is always non-NULL when we exit the loop.
>
> I have introduced a new "found" variable to say if we found the correct
> enty or not. I fixed one test by making it an else statement because
> that was more readable than testing "if (!found)".
>
> Fixes: 46e4b9ec4fa4 ("staging: vchiq_arm: use list_for_each_entry when accessing bulk_waiter_list")
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> ---
> .../vc04_services/interface/vchiq_arm/vchiq_arm.c | 12 +++++++-----
> 1 file changed, 7 insertions(+), 5 deletions(-)
This doesn't apply against my tree, what branch did you make it against?
thanks,
greg k-h
next prev parent reply other threads:[~2020-10-01 8:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 9:11 [PATCH] staging: vchiq: Fix list_for_each exit tests Dan Carpenter
2020-10-01 8:56 ` Greg Kroah-Hartman [this message]
2020-10-06 13:47 ` [PATCH v2] " Dan Carpenter
2020-10-08 9:38 ` Nicolas Saenz Julienne
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=20201001085650.GA1832570@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=jamal.k.shareef@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=marcgonzalez@google.com \
--cc=nsaenzjulienne@suse.de \
--cc=stefan.wahren@i2se.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).