From: "Mikael Starvik" <mikael.starvik@axis.com>
To: <linux-kernel@vger.kernel.org>
Cc: <akpm@osdl.org>
Subject: [RFC] Introducing a new sub-architecture
Date: Fri, 27 May 2005 08:15:56 +0200 [thread overview]
Message-ID: <BFECAF9E178F144FAEF2BF4CE739C66801B76457@exmail1.se.axis.com> (raw)
I'm about to submit a new sub-architecture under arch/cris and I would
like to get your input on how this is best done. I can see at least
3 alternatives:
1. All the patches goes to LKML. Lots of boring patches that most
people doesn't care about.
2. Send drivers to the driver subsystems maintainers for review
and then a big .tgz to Andrew.
3. Send the .tgz directly to Andrew without reviews from the
driver guys.
I leaning towards option 2, comments?
Except from the new sub-architecture there will also be patches
to the generic cris parts to add support for e.g. SMP and to
convert to the new IRQ framework.
Thanks!
/Mikael
next reply other threads:[~2005-05-27 6:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-27 6:15 Mikael Starvik [this message]
2005-05-27 6:58 ` Andrew Morton
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=BFECAF9E178F144FAEF2BF4CE739C66801B76457@exmail1.se.axis.com \
--to=mikael.starvik@axis.com \
--cc=akpm@osdl.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
all inboxes | Powered by JetHome®