From: "Guan Xuetao" <guanxuetao@mprc•pku.edu.cn>
To: 'Paul Mundt' <lethal@linux-sh•org>
Cc: sfr@canb•auug.org.au, 'Arnd Bergmann' <arnd@arndb•de>,
gregkh@suse•de, jbarnes@virtuousgeek•org,
dmitry.torokhov@gmail•com, dtor@mail•ru, rubini@cvml•unipv.it,
linux-arch@vger•kernel.org, linux-kernel@vger•kernel.org,
linux-fbdev@vger•kernel.org, linux-next@vger•kernel.org
Subject: RE: Request for unicore32 architecture codes to merge into linux-next
Date: Tue, 18 Jan 2011 17:33:44 +0800 [thread overview]
Message-ID: <01bf01cbb6f2$cdba4a70$692edf50$@mprc.pku.edu.cn> (raw)
In-Reply-To: <20110118091032.GA18525@linux-sh.org>
> -----Original Message-----
> From: linux-next-owner@vger•kernel.org [mailto:linux-next-owner@vger•kernel.org] On Behalf Of Paul Mundt
> Sent: Tuesday, January 18, 2011 5:11 PM
> To: Guan Xuetao
> Cc: sfr@canb•auug.org.au; 'Arnd Bergmann'; gregkh@suse•de; jbarnes@virtuousgeek•org; dmitry.torokhov@gmail•com; dtor@mail•ru;
> rubini@cvml•unipv.it; linux-arch@vger•kernel.org; linux-kernel@vger•kernel.org; linux-fbdev@vger•kernel.org; linux-
> next@vger•kernel.org
> Subject: Re: Request for unicore32 architecture codes to merge into linux-next
>
> On Tue, Jan 18, 2011 at 05:07:41PM +0800, Guan Xuetao wrote:
> > IMO, the whole architecture specific codes need to be merged first, and only some
> > necessary drivers are included under staging. Then, I could split the staging drivers
> > into corresponding mail-list, and then, additional drivers.
> > Otherwise, there are no architecture basic for drivers review.
> >
> That's of course fine so long as the driver changes are reasonably
> self-contained. The situation we want to avoid is that you end up with
> drivers that depend on some private infrastructure of API where not
> enough context is provided when the two are decoupled.
>
> In any event, the architecture bits are the most self-contained and have
> had the most review of anything in this series of patches, so it probably
> makes sense to work on getting those bits integrated and then dealing
> with the rest incrementally.
Then, I should:
1. merge reviewed arch dir and reviewed drivers (for now, i8042)
2. submit staging drivers to review
Am I right?
Thanks.
Guan Xuetao
next prev parent reply other threads:[~2011-01-18 9:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-15 17:00 Request for unicore32 architecture codes to merge into linux-next Guan Xuetao
2011-01-15 22:08 ` Dmitry Torokhov
2011-01-16 15:35 ` Guan Xuetao
2011-01-18 4:33 ` Paul Mundt
2011-01-18 9:07 ` Guan Xuetao
2011-01-18 9:10 ` Paul Mundt
2011-01-18 9:33 ` Guan Xuetao [this message]
2011-01-18 9:53 ` Paul Mundt
2011-01-18 18:33 ` Konrad Rzeszutek Wilk
2011-01-19 2:20 ` Guan Xuetao
2011-01-20 19:42 ` Jesse Barnes
2011-01-22 2:17 ` Guan Xuetao
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='01bf01cbb6f2$cdba4a70$692edf50$@mprc.pku.edu.cn' \
--to=guanxuetao@mprc$(echo .)pku.edu.cn \
--cc=arnd@arndb$(echo .)de \
--cc=dmitry.torokhov@gmail$(echo .)com \
--cc=dtor@mail$(echo .)ru \
--cc=gregkh@suse$(echo .)de \
--cc=jbarnes@virtuousgeek$(echo .)org \
--cc=lethal@linux-sh$(echo .)org \
--cc=linux-arch@vger$(echo .)kernel.org \
--cc=linux-fbdev@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rubini@cvml$(echo .)unipv.it \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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