From: Sam Ravnborg <sam@ravnborg.org>
To: 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: Fri, 4 Jun 2004 18:57:15 +0200 [thread overview]
Message-ID: <20040604165715.GB2388@mars.ravnborg.org> (raw)
In-Reply-To: <BFECAF9E178F144FAEF2BF4CE739C66818F497@exmail1.se.axis.com>
On Fri, Jun 04, 2004 at 07:46:21AM +0200, Mikael Starvik wrote:
> Hi,
>
> >Who reviewed the ethernet driver?
> >Who reviewed the IDE driver?
> >Has Bart seen this new driver?
> >Why was this committed without first being run by the subsystem
> maintainers?
>
> I am very happy if people outside Axis can find time to review patches
> that only affects the CRIS architecture (note that all files are under
> arch/cris and there is no way you can get these drivers unless you run
> CRIS). I have assumed that people like you and Bart have too much on
> your hands to do this. The few times I have tried to patch CRIS stuff on
> LKML the response is usally none.
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.
s390 has their own directory.
arm has their own directory under driver/net/ etc.
With respect to patches, a very good approach is to follow same style
as is done for s390.
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.
General rule is to make easy for the reader.
Sam
next prev parent reply other threads:[~2004-06-04 16:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BFECAF9E178F144FAEF2BF4CE739C668D0BC1E@exmail1.se.axis.com>
2004-06-04 5:46 ` Mikael Starvik
2004-06-04 16:57 ` Sam Ravnborg [this message]
2004-06-04 23:25 ` Bartlomiej Zolnierkiewicz
[not found] <BFECAF9E178F144FAEF2BF4CE739C668D47C24@exmail1.se.axis.com>
2004-06-07 5:53 ` Mikael Starvik
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] <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=20040604165715.GB2388@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
all inboxes | Powered by JetHome®