[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220321084844.GG3293@kadam>
Date: Mon, 21 Mar 2022 11:48:45 +0300
From: Dan Carpenter <dan.carpenter@...cle.com>
To: Jakob Koschel <jakobkoschel@...il.com>
Cc: Vaibhav Agarwal <vaibhav.sr@...il.com>,
linux-kernel@...r.kernel.org, greybus-dev@...ts.linaro.org,
linux-staging@...ts.linux.dev, Mark Greer <mgreer@...malcreek.com>,
Johan Hovold <johan@...nel.org>, Alex Elder <elder@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Mike Rapoport <rppt@...nel.org>,
Brian Johannesmeyer <bjohannesmeyer@...il.com>,
Cristiano Giuffrida <c.giuffrida@...nl>,
"Bos, H.J." <h.j.bos@...nl>
Subject: Re: [PATCH] staging: greybus: codecs: fix type confusion with
dedicated list iterator variable
The subject says that it fixes a bug but it does not.
On Sat, Mar 19, 2022 at 09:20:58PM +0100, Jakob Koschel wrote:
> If the list does not exit early then data == NULL and 'module' does not
> point to a valid list element.
> Using 'module' in such a case is not valid and was therefore removed.
This paragraph is confusing jumble words. Just say: "This code is fine".
>
> In preparation to limit the scope of the list iterator to the list
> traversal loop, use a dedicated pointer pointing to the found element [1].
This paragraph is the information we need. Just add something like
"This patch has no effect on runtime".
regards,
dan carpenter
Powered by blists - more mailing lists