[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <08979629-d9b8-6656-222f-4e84667651a1@web.de>
Date: Sun, 19 Apr 2020 18:19:12 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Dejin Zheng <zhengdejin5@...il.com>, linux-can@...r.kernel.org,
netdev@...r.kernel.org, "David S. Miller" <davem@...emloft.net>,
Marc Kleine-Budde <mkl@...gutronix.de>,
Wolfgang Grandegger <wg@...ndegger.com>
Cc: linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org,
Coccinelle <cocci@...teme.lip6.fr>
Subject: Re: [PATCH net-next v1] can: ti_hecc: convert to
devm_platform_ioremap_resource_byname()
> use devm_platform_ioremap_resource_byname() to simplify code,
> it contains platform_get_resource_byname() and
> devm_ioremap_resource(), and also remove some duplicate error
> message.
How do you think about a wording variant like the following?
Use the function “devm_platform_ioremap_resource_byname” to simplify
source code which calls the functions “platform_get_resource_byname”
and “devm_ioremap_resource”.
Remove also a few error messages which became unnecessary with this
software refactoring.
Will any more contributors get into the development mood to achieve
similar collateral evolution by the means of the semantic patch language?
Would you like to increase applications of the Coccinelle software?
Regards,
Markus
Powered by blists - more mailing lists