From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Miklos Szeredi <mszeredi@suse.cz>,
Maxim Krasnyansky <maxk@qualcomm.com>,
Jeff Dike <jdike@karaya.com>,
kernel-janitors@vger.kernel.org, Jason Lunz <lunz@falooley.org>,
Jan Beulich <jbeulich@novell.com>, Andi Kleen <ak@suse.de>,
vtun@office.satix.net, Jens Axboe <jens.axboe@oracle.com>,
Stephen Hemminger <shemminger@linux-foundation.org>,
Nick Piggin <npiggin@suse.de>,
Davide Brini <davide.brini@unibo.it>,
Fernando Luis Vazquez Cao <fernando@oss.ntt.co.jp>,
virtualization@lists.osdl.org, Ingo Molnar <mingo@elte.hu>,
Alexey Dobriyan <adobriyan@gmail.com>,
Zachary Amsden <zach@vmware.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Jeff Dike <jdike@addtoit.com>,
Rusty Russell <rusty@rustcorp.com.au>,
Eduard-Gabriel Munteanu <maxdamage@aladin.ro>,
Chris Wright <chrisw@sous-sol.org>,
user-mode-linux-user@lists.sourceforge.net,
Jeff Dike <jdike@linux.intel.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Jeremy Fitzhardinge <jeremy@xensource.com>,
Haavard Skinnemoen <hskinnemoen@atmel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [uml-devel] [PATCH 1/5] um/... convert #include "linux/..." to #include <linux/...>
Date: Tue, 21 Aug 2007 19:09:17 +0200 [thread overview]
Message-ID: <200708211909.23027.blaisorblade@yahoo.it> (raw)
In-Reply-To: <1187561903.4200.138.camel@localhost>
[-- Attachment #1.1: Type: text/plain, Size: 1126 bytes --]
On lunedì 20 agosto 2007, Joe Perches wrote:
> (untested)
>
> There are several files that
> #include "linux/file" not #include <linux/file>
> #include "asm/file" not #include <asm/file>
>
> Here's a little script that converts them:
>
> egrep -i -r -l --include=*.[ch] \
> "^[[:space:]]*\#[[:space:]]*include[[:space:]]*\"(linux|asm)/(.*)\"" * \
>
> | xargs sed -i -e
> | 's/^[[:space:]]*#[[:space:]]*include[[:space:]]*"\(linux\|asm\)\/\(.*\)"/
> |#include <\1\/\2>/g'
>
> Signed-off-by: Joe Perches <joe@perches.com>
Wait, this patch may or may not be sane (Jeff will tell more I guess). Since
we use two different sets of headers (the host ones from userspace and the
guest ones from Linux), this peculiar style has been used till now to make
clear the difference (#include <file> is used for host headers) - at least
that's what I think (I've never asked to Jeff, but I silently deduced this
and followed this practice).
--
"Doh!" (cit.), I've made another another mistake!
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 315 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
[-- Attachment #3: Type: text/plain, Size: 194 bytes --]
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2007-08-21 17:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-19 22:18 [uml-devel] [PATCH 1/5] um/... convert #include "linux/..." to #include <linux/...> Joe Perches
2007-08-21 17:09 ` Blaisorblade [this message]
2007-08-22 16:25 ` Jeff Dike
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=200708211909.23027.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=adobriyan@gmail.com \
--cc=ak@suse.de \
--cc=chrisw@sous-sol.org \
--cc=davide.brini@unibo.it \
--cc=fernando@oss.ntt.co.jp \
--cc=hskinnemoen@atmel.com \
--cc=jbeulich@novell.com \
--cc=jdike@addtoit.com \
--cc=jdike@karaya.com \
--cc=jdike@linux.intel.com \
--cc=jens.axboe@oracle.com \
--cc=jeremy@xensource.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lunz@falooley.org \
--cc=maxdamage@aladin.ro \
--cc=maxk@qualcomm.com \
--cc=mingo@elte.hu \
--cc=mszeredi@suse.cz \
--cc=npiggin@suse.de \
--cc=rusty@rustcorp.com.au \
--cc=shemminger@linux-foundation.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=user-mode-linux-user@lists.sourceforge.net \
--cc=virtualization@lists.osdl.org \
--cc=vtun@office.satix.net \
--cc=zach@vmware.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