From: "Mikael Starvik" <mikael.starvik@axis.com>
To: "'Sam Ravnborg'" <sam@ravnborg.org>,
"'Mikael Starvik'" <mikael.starvik@axis.com>
Cc: "'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 07:53:30 +0200 [thread overview]
Message-ID: <BFECAF9E178F144FAEF2BF4CE739C66818F49D@exmail1.se.axis.com> (raw)
In-Reply-To: <BFECAF9E178F144FAEF2BF4CE739C668D47C24@exmail1.se.axis.com>
>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...). Generally we don't expect people to take attention
about CRIS when making changes but it is of course nice when it
happens.
>Smaller logical splitted patches, being sent out after each kernel release.
>This allows LKML readers to do peer review of changes to the IDE driver,
>without having to step over a lot of unrelated code.
Sure. More work for me but I'll also get more valuable feedback
and that is important.
/Mikael
next parent reply other threads:[~2004-06-07 5:54 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 ` Mikael Starvik [this message]
2004-06-07 18:43 ` Sam Ravnborg
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=BFECAF9E178F144FAEF2BF4CE739C66818F49D@exmail1.se.axis.com \
--to=mikael.starvik@axis.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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
all inboxes | Powered by JetHome®