From: Pekka Enberg <penberg@kernel.org>
To: Joe Perches <joe@perches.com>
Cc: "Luis R. Rodriguez" <lrodriguez@atheros.com>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
devel@driverdev.osuosl.org, mcgrof@gmail.com,
Julia Lawall <julia@diku.dk>, Nicolas Palix <npalix@diku.dk>,
Yoann Padioleau <yoann.padioleau@gmail.com>
Subject: Re: [PATCH v2] scripts: add typdef removal tool
Date: Sun, 19 Sep 2010 12:30:23 +0300 [thread overview]
Message-ID: <4C95D82F.2080001@kernel.org> (raw)
In-Reply-To: <1284886192.1778.94.camel@Joe-Laptop>
On 19.9.2010 11.49, Joe Perches wrote:
> On Sun, 2010-09-19 at 11:19 +0300, Pekka Enberg wrote:
>> On Fri, Aug 14, 2009 at 8:39 AM, Luis R. Rodriguez
>> <lrodriguez@atheros.com> wrote:
>>> If you are porting drivers and need to remove tydpefs you can use
>>> this to help you port the driver faster. Until we don't have a fully
>>> correct and complete way to do this through Coccinelle spatch we
>>> might as well help developers porting drivers with something. spatch
>>> also has a learning curve, people working on staging may not end
>>> up using it for a while.
>> How come this script never made it to the kernel tree?
> General lack of interest?
>
> Probably the same reason that similar patches didn't.
> https://patchwork.kernel.org/patch/88026/
Scripts like these are sure handy when dealing with the crap in staging
tree. Maybe we can convince Greg to take them in.
Pekka
next prev parent reply other threads:[~2010-09-19 9:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-14 5:39 [PATCH v2] scripts: add typdef removal tool Luis R. Rodriguez
2009-08-17 6:02 ` Amerigo Wang
2009-08-21 8:48 ` Jiri Slaby
2009-08-23 13:09 ` Matthias Urlichs
2009-08-23 16:06 ` Américo Wang
2009-08-23 13:22 ` Matthias Urlichs
2009-08-23 16:04 ` Américo Wang
2009-08-23 17:59 ` Jiri Slaby
2009-08-25 14:35 ` Matthias Urlichs
2010-09-19 8:19 ` Pekka Enberg
2010-09-19 8:49 ` Joe Perches
2010-09-19 9:30 ` Pekka Enberg [this message]
2010-09-19 15:03 ` Luis R. Rodriguez
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=4C95D82F.2080001@kernel.org \
--to=penberg@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=joe@perches.com \
--cc=julia@diku.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=lrodriguez@atheros.com \
--cc=mcgrof@gmail.com \
--cc=npalix@diku.dk \
--cc=yoann.padioleau@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