From: Helge Deller <deller@gmx.de>
To: Jakob Koschel <jakobkoschel@gmail.com>
Cc: linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.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] video: fbdev-MMP: replace usage of found with dedicated list iterator variable
Date: Tue, 12 Apr 2022 22:06:59 +0200 [thread overview]
Message-ID: <d90f37a3-e91a-c2a2-e349-5f835b048e5b@gmx.de> (raw)
In-Reply-To: <20220331223503.902142-1-jakobkoschel@gmail.com>
On 4/1/22 00:35, 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/ [1]
> Signed-off-by: Jakob Koschel <jakobkoschel@gmail.com>
applied.
Thanks!
Helge
> ---
> drivers/video/fbdev/mmp/core.c | 11 +++++------
> 1 file changed, 5 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/video/fbdev/mmp/core.c b/drivers/video/fbdev/mmp/core.c
> index 154127256a2c..03707461eced 100644
> --- a/drivers/video/fbdev/mmp/core.c
> +++ b/drivers/video/fbdev/mmp/core.c
> @@ -127,19 +127,18 @@ EXPORT_SYMBOL_GPL(mmp_unregister_panel);
> */
> struct mmp_path *mmp_get_path(const char *name)
> {
> - struct mmp_path *path;
> - int found = 0;
> + struct mmp_path *path = NULL, *iter;
>
> mutex_lock(&disp_lock);
> - list_for_each_entry(path, &path_list, node) {
> - if (!strcmp(name, path->name)) {
> - found = 1;
> + list_for_each_entry(iter, &path_list, node) {
> + if (!strcmp(name, iter->name)) {
> + path = iter;
> break;
> }
> }
> mutex_unlock(&disp_lock);
>
> - return found ? path : NULL;
> + return path;
> }
> EXPORT_SYMBOL_GPL(mmp_get_path);
>
>
> base-commit: f82da161ea75dc4db21b2499e4b1facd36dab275
prev parent reply other threads:[~2022-04-12 20:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 22:35 Jakob Koschel
2022-04-12 20:06 ` Helge Deller [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=d90f37a3-e91a-c2a2-e349-5f835b048e5b@gmx.de \
--to=deller@gmx.de \
--cc=bjohannesmeyer@gmail.com \
--cc=c.giuffrida@vu.nl \
--cc=dri-devel@lists.freedesktop.org \
--cc=h.j.bos@vu.nl \
--cc=jakobkoschel@gmail.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rppt@kernel.org \
/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
all inboxes | Powered by JetHome®