[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c030d093-56d9-1437-fce5-315c960e61d2@kernel.org>
Date: Sun, 25 Sep 2016 09:45:21 +0100
From: Jonathan Cameron <jic23@...nel.org>
To: SF Markus Elfring <elfring@...rs.sourceforge.net>
Cc: linux-iio@...r.kernel.org, Hartmut Knaack <knaack.h@....de>,
Lars-Peter Clausen <lars@...afoo.de>,
Peter Meerwald-Stadler <pmeerw@...erw.net>,
LKML <linux-kernel@...r.kernel.org>,
kernel-janitors@...r.kernel.org,
Julia Lawall <julia.lawall@...6.fr>
Subject: Re: iio: Rename a jump label in iio_buffer_store_watermark()
On 24/09/16 20:21, SF Markus Elfring wrote:
>> I'm not necessarily against this change which does perhaps clarify the code
>> ever so slightly,
>
> Thanks for another bit of positive feedback.
>
>
>> but I am interested to know where 'current Linux coding style convention' comes from?
>
> How often do you check the status of a document like "CodingStyle" for example? ;-)
Every time I see a patch doing a style change I don't remember being there last time
I looked ;)
I'm not seeing this one in there. Which tool is spitting it out? Or is
the test yours?
>
> How do you think about information from a commit like
> "docs: Remove space-before-label guidance from CodingStyle" (on 2016-09-21)?
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/Documentation/CodingStyle?id=79c70c304b0b443429b2a0019518532c5162817a
Yeah, I saw the discussion / flame war that resulted in that revert...
>
> Regards,
> Markus
>
Powered by blists - more mailing lists