From: Joe Perches <joe@perches.com>
To: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Andy Whitcroft <apw@shadowen.org>
Subject: convert #include "linux/..." to #include <linux/...> [PATCH]s follow
Date: Sun, 19 Aug 2007 15:17:44 -0700 [thread overview]
Message-ID: <1187561864.4200.136.camel@localhost> (raw)
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'
Maybe a similar check could be added to checkpatch.pl
next reply other threads:[~2007-08-19 22:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-19 22:17 Joe Perches [this message]
2007-08-19 22:19 ` convert #include "linux/..." to #include <linux/...> [PATCH]s follow Jesper Juhl
2007-08-19 22:33 ` Jan Engelhardt
2007-08-19 22:44 ` Al Viro
2007-08-19 22:49 ` Joe Perches
2007-08-19 22:58 ` Al Viro
2007-08-19 23:05 ` Joe Perches
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=1187561864.4200.136.camel@localhost \
--to=joe@perches.com \
--cc=apw@shadowen.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).