[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180717101329.yl4hwob2jbjlp2uh@mwanda>
Date: Tue, 17 Jul 2018 13:13:29 +0300
From: Dan Carpenter <dan.carpenter@...cle.com>
To: Todd Poynor <toddpoynor@...il.com>
Cc: Rob Springer <rspringer@...gle.com>,
John Joseph <jnjoseph@...gle.com>,
Ben Chan <benchan@...omium.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
devel@...verdev.osuosl.org, Zhongze Hu <frankhu@...omium.org>,
linux-kernel@...r.kernel.org, Simon Que <sque@...omium.org>,
Guenter Roeck <groeck@...omium.org>,
Todd Poynor <toddpoynor@...gle.com>,
Dmitry Torokhov <dtor@...omium.org>
Subject: Re: [PATCH 12/32] staging: gasket: gasket_wait_with_reschedule
return when condition hit
On Mon, Jul 16, 2018 at 07:09:06PM -0700, Todd Poynor wrote:
> From: Todd Poynor <toddpoynor@...gle.com>
>
> Return right away instead of break out of while and then return.
>
You could remove the (retries == max_retries) condition since that's
always true now and pull that code in one tab. You could do it in one
patch because they're closely related so it's One Thing [tm].
regads,
dan carpenter
Powered by blists - more mailing lists