From: Artem Bityutskiy <dedekind1@gmail.com>
To: Barry Song <21cnbao@gmail.com>
Cc: Barry Song <Barry.Song@csr.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
workgroup.linux@csr.com
Subject: Re: [PATCH 0/3] platform: add platform_devm_request_and_ioremap() common API
Date: Tue, 31 Jan 2012 15:23:45 +0200 [thread overview]
Message-ID: <1328016225.28171.7.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1328015763.28171.2.camel@sauron.fi.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]
On Tue, 2012-01-31 at 15:16 +0200, Artem Bityutskiy wrote:
> On Tue, 2012-01-31 at 20:57 +0800, Barry Song wrote:
> > > If yes, I think it would be nice of you to give a credit to coccinelle
> > > and its authors for developing this awesome tool in every commit
> > > message.
> >
> > devm_request_and_ioremap() is still something new by commit
>
> Ah, ok. But it would be cool if you could create a coccinell semantic
> patch for this, although I should admit this is not very easy, but a lot
> of fun.
To promote the idea further. If you manage to create a semantic patch
for this, then you will just generate your patches automatically. You
will also be able to make it more probable that people will use this new
api by adding your semantic patch to scripts/coccinelle/api.
I do not know how many people run coccinelle, but I recently started to
check all incoming MTD patches with coccinelle before applying them. A
little bit of scripting and this becomes easy to do.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-01-31 13:21 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 9:59 [PATCH 0/3] platform: add platform_devm_request_and_ioremap() common API Barry Song
2012-01-31 10:00 ` [PATCH 1/3] platform: add common resource requesting and mapping helper Barry Song
2012-01-31 10:17 ` Wolfram Sang
2012-01-31 11:04 ` Barry Song
2012-01-31 11:33 ` Wolfram Sang
2012-01-31 12:09 ` Barry Song
2012-01-31 20:34 ` Grant Likely
2012-01-31 21:15 ` Wolfram Sang
2012-01-31 21:51 ` Grant Likely
2012-02-01 2:11 ` Barry Song
2012-02-01 10:03 ` Wolfram Sang
2012-02-01 10:20 ` Barry Song
2012-02-01 12:56 ` Mark Brown
2012-02-02 0:10 ` Grant Likely
2012-01-31 20:35 ` Grant Likely
2012-01-31 21:20 ` Linus Walleij
2012-01-31 21:52 ` Grant Likely
2012-02-01 2:22 ` Barry Song
2012-01-31 10:00 ` [PATCH 2/3] GPIO: TEGRA: move to use platform_devm_request_and_ioremap() helper Barry Song
2012-01-31 16:55 ` Stephen Warren
2012-01-31 20:37 ` Grant Likely
2012-01-31 10:00 ` [PATCH 3/3] MTD: NAND: txx9ndfmc: " Barry Song
2012-01-31 11:14 ` [PATCH 0/3] platform: add platform_devm_request_and_ioremap() common API Artem Bityutskiy
2012-01-31 12:57 ` Barry Song
2012-01-31 13:16 ` Artem Bityutskiy
2012-01-31 13:23 ` Artem Bityutskiy [this message]
2012-01-31 13:27 ` Wolfram Sang
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=1328016225.28171.7.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=21cnbao@gmail.com \
--cc=Barry.Song@csr.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=workgroup.linux@csr.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;
as well as URLs for NNTP newsgroup(s).