From: Markus Elfring <Markus.Elfring@web.de>
To: Dejin Zheng <zhengdejin5@gmail.com>, netdev@vger.kernel.org
Cc: linux-can@vger.kernel.org, linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Marc Kleine-Budde <mkl@pengutronix.de>,
Wolfgang Grandegger <wg@grandegger.com>
Subject: Re: [net-next v2] can: ti_hecc: convert to devm_platform_ioremap_resource_byname()
Date: Mon, 20 Apr 2020 17:42:04 +0200 [thread overview]
Message-ID: <a6fbdb0b-60be-baae-ad17-1977ed12fdaa@web.de> (raw)
In-Reply-To: <20200420151911.GA2698@nuc8i5>
>> If you would use another script (like for the semantic patch language),
>> you could find remaining update candidates in a convenient way,
>> couldn't you?
>>
> Markus, could you share the script?
Theoretically, yes.
Practically, I would prefer additional development options.
* I am trying for a while to improve some components also by advanced
applications of the Coccinelle software.
I hope to increase incentives for involved contributors.
* I imagine that a known directory would be a nice place for
further reuse of such SmPL scripts.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/scripts/coccinelle?id=ae83d0b416db002fe95601e7f97f64b59514d936
* How will your motivation evolve?
+ Pick more updates for your own contribution statistics.
And / Or
+ Tell more interested parties about change possibilities.
Regards,
Markus
prev parent reply other threads:[~2020-04-20 15:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 13:22 [PATCH net-next v2] can: ti_hecc: convert to devm_platform_ioremap_resource_byname() Dejin Zheng
2020-04-20 14:00 ` [net-next " Markus Elfring
2020-04-20 14:19 ` Dejin Zheng
2020-04-20 14:54 ` Markus Elfring
2020-04-20 15:19 ` Dejin Zheng
2020-04-20 15:42 ` Markus Elfring [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a6fbdb0b-60be-baae-ad17-1977ed12fdaa@web.de \
--to=markus.elfring@web.de \
--cc=davem@davemloft.net \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=wg@grandegger.com \
--cc=zhengdejin5@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox