From: Julia Lawall <julia@diku.dk>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Nicolas Palix <npalix@diku.dk>
Subject: Re: Typedef removal tool
Date: Wed, 12 Aug 2009 07:01:52 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0908120659001.32131@ask.diku.dk> (raw)
In-Reply-To: <43e72e890908111418m47910085k2d0016e2add8914f@mail.gmail.com>
On Tue, 11 Aug 2009, Luis R. Rodriguez wrote:
> Anyone know if there is a typedef removal tool? When porting drivers
> this needs to be done quite often.
>
> FWIW I've started porting some driver and have come across some tools,
> or written my own scripts, which have helped. Using spatch to port a
> driver was such a tool I explored. I think I'll try to put together
> some info on the driver project wiki for this. typdef removal tool
> would still be neat.
Nicolas Palix (in CC) did a bit of work on this recently using Coccinelle,
but the problem is that simply removing the typedef is not enough, one has
to come up with a name that is within the spirit of the names used in
Linux, or perhaps recognize that the structure in question already exists
in a more general form in the kernel an thus the declaration should be
removed completely.
Someone else made a dedicated tool using a dictionary of the old and new
names that at least partially addresses these problems. Nicolas knows who
that person is.
julia
next prev parent reply other threads:[~2009-08-12 5:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-11 21:18 Typedef removal tool Luis R. Rodriguez
2009-08-12 5:01 ` Julia Lawall [this message]
2009-08-12 7:45 ` Luis R. Rodriguez
2009-08-12 12:23 ` Nicolas Palix
2009-08-12 15:45 ` Luis R. Rodriguez
2009-08-12 15:57 ` Julia Lawall
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=Pine.LNX.4.64.0908120659001.32131@ask.diku.dk \
--to=julia@diku.dk \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=npalix@diku.dk \
/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