[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f573b2d3-11d0-92b5-f8ab-4c4b6493e152@metux.net>
Date: Tue, 11 Jun 2019 22:40:25 +0200
From: "Enrico Weigelt, metux IT consult" <lkml@...ux.net>
To: Markus Elfring <Markus.Elfring@....de>,
Julia Lawall <julia.lawall@...6.fr>,
Himanshu Jha <himanshujha199640@...il.com>
Cc: cocci@...teme.lip6.fr, kernel-janitors@...r.kernel.org,
linux-kernel@...r.kernel.org,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Bartosz Golaszewski <bgolaszewski@...libre.com>,
Gilles Muller <Gilles.Muller@...6.fr>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Linus Walleij <linus.walleij@...aro.org>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
Michal Marek <michal.lkml@...kovi.net>,
Nicolas Palix <nicolas.palix@...g.fr>
Subject: Re: Coccinelle: api: add devm_platform_ioremap_resource script
On 09.06.19 10:55, Markus Elfring wrote:
<snip>
>> But there is not usually any interesting formatting on the left side of an
>> assignment (ie typically no newlines or comments).
>
> Is there any need to trigger additional source code reformatting?
>
>> I can see no purpose to factorizing the right parenthesis.
>
> These characters at the end of such a function call should be kept unchanged.
Agreed. OTOH, we all know that spatch results still need to be carefully
checked. I suspect trying to teach it all the formatting rules of the
kernel isn't an easy task.
> The flag “IORESOURCE_MEM” is passed as the second parameter for the call
> of the function “platform_get_resource” in this refactoring.
In that particular case, we maybe should consider separate inline
helpers instead of passing this is a parameter.
Maybe it would even be more efficient to have completely separate
versions of devm_platform_ioremap_resource(), so we don't even have
to pass that parameter on stack.
--mtx
--
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@...ux.net -- +49-151-27565287
Powered by blists - more mailing lists