[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7b4fe770-dadd-80ba-2ba4-0f2bc90984ef@web.de>
Date: Sun, 9 Jun 2019 10:55:32 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: 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
>>> +- e1 = devm_ioremap_resource(arg4, id);
>>> ++ e1 = devm_platform_ioremap_resource(arg1, arg3);
>>
>> Can the following specification variant matter for the shown SmPL
>> change approach?
>>
>> + e1 =
>> +- devm_ioremap_resource(arg4, id
>> ++ devm_platform_ioremap_resource(arg1, arg3
>> + );
>
> In the latter case, the original formatting of e1 will be preserved.
I would like to point the possibility out to express only required changes
also by SmPL specifications.
> 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.
I got another software development concern according to the discussed
software update “drivers: provide devm_platform_ioremap_resource()”
(from 2019-02-21).
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/base/platform.c?id=7945f929f1a77a1c8887a97ca07f87626858ff42
The flag “IORESOURCE_MEM” is passed as the second parameter for the call
of the function “platform_get_resource” in this refactoring.
Should this detail be specified also in the proposed script for the
semantic patch language instead of using the metavariable “arg2”
in SmPL disjunctions?
How do you think about to delete error detection and corresponding
exception handling code for the previous function call?
Is the SmPL code specification “when != id” really sufficient for
the exclusion of variable reassignments here?
Regards,
Markus
Powered by blists - more mailing lists