From: Sam Ravnborg <sam@ravnborg.org>
To: Mikael Starvik <mikael.starvik@axis.com>
Cc: "'Sam Ravnborg'" <sam@ravnborg.org>,
"'Jeff Garzik'" <jgarzik@pobox.com>,
"'Andrew Morton'" <akpm@osdl.org>,
"'Linux Kernel'" <linux-kernel@vger.kernel.org>,
"'Bartlomiej Zolnierkiewicz'" <B.Zolnierkiewicz@elka.pw.edu.pl>
Subject: Re: [PATCH] CRIS architecture update
Date: Mon, 7 Jun 2004 20:43:09 +0200 [thread overview]
Message-ID: <20040607184309.GA3152@mars.ravnborg.org> (raw)
In-Reply-To: <BFECAF9E178F144FAEF2BF4CE739C66818F49D@exmail1.se.axis.com>
On Mon, Jun 07, 2004 at 07:53:30AM +0200, Mikael Starvik wrote:
> >The general rule is to locate drivers under drivers/, even the arch
> >specific ones. This allows for easier grepping after users of a
> >given API etc.
>
> Ok, if that is a general rule I can move them (but the patch will
> be large...).
Please do so. As Bartlomiej note the rule is to keep drivers under:
drivers/<subsystem>/<arch>
The most efficient way to do the move is to send Linus a direct
mail with a simple shell script that does the moving of the files.
Along the lines of:
mkdir -p drivers/ide/cris
mv arch/cris/drivers/ide/* drivers/ide/cris
etc.
Sam
next prev parent reply other threads:[~2004-06-07 18:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BFECAF9E178F144FAEF2BF4CE739C668D47C24@exmail1.se.axis.com>
2004-06-07 5:53 ` [PATCH] CRIS architecture update Mikael Starvik
2004-06-07 18:43 ` Sam Ravnborg [this message]
2004-06-07 19:00 ` Bartlomiej Zolnierkiewicz
[not found] <BFECAF9E178F144FAEF2BF4CE739C668D47E56@exmail1.se.axis.com>
2004-06-07 5:42 ` Mikael Starvik
[not found] <BFECAF9E178F144FAEF2BF4CE739C668D0BC1E@exmail1.se.axis.com>
2004-06-04 5:46 ` Mikael Starvik
2004-06-04 16:57 ` Sam Ravnborg
2004-06-04 23:25 ` Bartlomiej Zolnierkiewicz
[not found] <200406031419.i53EJgVI027812@hera.kernel.org>
2004-06-03 15:41 ` Jeff Garzik
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=20040607184309.GA3152@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikael.starvik@axis.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