[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAO3upoZZeYZySN03=E4ubUf=a8_EOc3i9KpTMmfR1yCHoo8AjQ@mail.gmail.com>
Date: Tue, 17 Jul 2018 12:53:09 -0700
From: Todd Poynor <toddpoynor@...il.com>
To: Dan Carpenter <dan.carpenter@...cle.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>,
lkml <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 Tue, Jul 17, 2018 at 4:12 AM, Dan Carpenter <dan.carpenter@...cle.com> wrote:
> On Tue, Jul 17, 2018 at 01:13:29PM +0300, Dan Carpenter wrote:
>> 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.
>> >
>>
>
> Btw, I wasn't going to complain about this but since Greg is being extra
> critical about commit messages that don't explain *why* it just creates
> an environment why I also feel free to complain... I couldn't
> understand what this commit does without looking at the code in context.
>
> A possible commit message here is:
>
> [PATCH 12/32] staging: gasket: small cleanup in gasket_wait_with_reschedule()
>
> gasket_wait_with_reschedule() is a little more clear if we just return
> directly.
I've updated the text for v3, thanks -- Todd
>
> regards,
> dan carpenter
>
--
Todd
Powered by blists - more mailing lists