From: 21cnbao@gmail.com (Barry Song)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] ARM Subarchitecture group maintainership
Date: Thu, 19 May 2011 22:23:43 +0800 [thread overview]
Message-ID: <BANLkTikKhZu_H_QT+Uds22sepk1OnEeDNA@mail.gmail.com> (raw)
In-Reply-To: <201105191550.20129.arnd@arndb.de>
2011/5/19 Arnd Bergmann <arnd@arndb.de>:
> On Thursday 19 May 2011, Barry Song wrote:
>> 2011/5/19 Nicolas Pitre <nico@fluxnic.net>:
>> > On Thu, 19 May 2011, Barry Song wrote:
>> > Something like that. ?The exact details will be fleshed out as we go.
>> > The idea is to give a round of review from a higher point of view to
>> > make sure no opportunities for code reuse is missed, etc. ?The mechanics
>> > of how this code transitions from this tree into mainline during the
>> > merge window is secondary.
>>
>> i asked this because we wanted to send the source codes of
>> CSR(http://www.csr.com) to upstream as i have told you in LDS. it
>> looks like we need to follow the below new changes to make our source
>> codes acceptable?
>> 1. arm device tree
>> 2. new pinmux framework from Linus Walleij
>> 3. move GPIO from plat/mach to drivers/gpio?
>
> I would count at least the last two as mandatory, for the device tree,
> it depends on how much work it would be for you to do the conversion
> and at what time you submit the series. The longer you wait before
> submitting the series, the stricter the requirements will get.
>
> Do you have a diffstat or a git tree with your work available?
not yet by now. it should be coming in the middle of next month. we
have workable codes but need a lot of refinations before sending
patches for review. it is more like a new begin from scratch, so
arm/arch changes should be things we can catch.
>
> ? ? ? ?Arnd
>
next prev parent reply other threads:[~2011-05-19 14:23 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 8:47 [RFC] ARM Subarchitecture group maintainership Arnd Bergmann
2011-05-18 14:53 ` Catalin Marinas
2011-05-25 7:59 ` Tony Lindgren
2011-05-25 14:28 ` Nicolas Pitre
2011-05-25 15:34 ` Tony Lindgren
2011-05-25 16:06 ` Thomas Gleixner
2011-05-26 8:28 ` Mark Brown
2011-05-26 8:33 ` Thomas Gleixner
2011-05-26 9:59 ` Mark Brown
2011-05-26 10:13 ` Arnd Bergmann
2011-05-18 15:22 ` Shawn Guo
2011-05-18 15:27 ` Anca Emanuel
2011-05-19 12:13 ` Arnd Bergmann
2011-05-18 15:56 ` Jean-Christophe PLAGNIOL-VILLARD
2011-05-18 21:24 ` Thomas Gleixner
2011-05-18 21:47 ` Catalin Marinas
2011-05-18 20:49 ` David Brown
2011-05-19 1:27 ` Barry Song
2011-05-19 2:42 ` Nicolas Pitre
2011-05-19 3:01 ` Barry Song
2011-05-19 13:31 ` Linus Walleij
2011-05-19 19:28 ` Russell King - ARM Linux
2011-05-19 19:31 ` Nicolas Pitre
2011-05-19 13:50 ` Arnd Bergmann
2011-05-19 14:23 ` Barry Song [this message]
2011-05-19 15:08 ` Arnd Bergmann
2011-05-24 9:23 ` Barry Song
2011-05-24 12:26 ` Arnd Bergmann
2011-05-27 5:34 ` viresh kumar
2011-05-27 7:24 ` Arnd Bergmann
2011-05-19 12:20 ` Arnd Bergmann
2011-05-19 3:38 ` viresh kumar
2011-05-20 20:48 ` Linus Walleij
2011-05-20 20:59 ` Joe Perches
2011-05-21 8:23 ` Arnd Bergmann
2011-05-25 8:10 ` Nicolas Ferre
2011-05-25 8:23 ` Sascha Hauer
2011-05-25 16:19 ` H Hartley Sweeten
2011-05-26 16:14 ` Kevin Hilman
2011-05-27 0:01 ` Kyungmin Park
2011-07-26 18:03 ` Stephen Boyd
2011-07-27 1:47 ` Barry Song
2011-07-27 2:23 ` Stephen Boyd
2011-07-27 14:55 ` Arnd Bergmann
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=BANLkTikKhZu_H_QT+Uds22sepk1OnEeDNA@mail.gmail.com \
--to=21cnbao@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).