From: swetland@google.com (Brian Swetland)
To: linux-arm-kernel@lists.infradead.org
Subject: board/device file names, and machine names
Date: Tue, 2 Mar 2010 15:38:44 -0800 [thread overview]
Message-ID: <a55d774e1003021538n5225b302ue1e77ea5e4f39fcc@mail.gmail.com> (raw)
In-Reply-To: <1267572545.8759.121.camel@c-dwalke-linux.qualcomm.com>
On Tue, Mar 2, 2010 at 3:29 PM, Daniel Walker <dwalker@codeaurora.org> wrote:
>> This seems like an unforunate issue to bikeshed about, and by
>> insisting on renaming the board names, more hurdles are put up between
>> the (often competing, at least for our time) goals of "going to
>> mainline" and "maintaining an up to date tree that works on production
>> hardware without regression".
>
> This is really a classic kind of issue .. If you work with us (i.e. the
> community) , then your code goes into the kernel. If you ignore us, then
> your code usually doesn't go in ..
Alrighty then.
Brian
next prev parent reply other threads:[~2010-03-02 23:38 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 21:29 board/device file names, and machine names Daniel Walker
2010-03-02 22:56 ` Brian Swetland
2010-03-02 23:29 ` Daniel Walker
2010-03-02 23:38 ` Brian Swetland [this message]
2010-03-03 3:42 ` Bill Gatliff
2010-03-03 3:36 ` Bill Gatliff
2010-03-03 8:00 ` Brian Swetland
2010-03-03 19:08 ` Theodore Tso
2010-03-03 19:22 ` Theodore Tso
2010-03-03 19:24 ` Russell King - ARM Linux
2010-03-02 23:51 ` Russell King - ARM Linux
2010-03-03 0:39 ` Daniel Walker
2010-03-03 0:47 ` Tim Bird
2010-03-03 0:52 ` Daniel Walker
2010-03-03 1:01 ` Brian Swetland
2010-03-03 3:52 ` Bill Gatliff
2010-03-03 8:42 ` Russell King - ARM Linux
2010-03-03 9:17 ` Pavel Machek
2010-03-03 9:47 ` Russell King - ARM Linux
2010-03-03 10:00 ` Pavel Machek
2010-03-03 10:08 ` Russell King - ARM Linux
2010-03-03 10:18 ` Pavel Machek
2010-03-03 10:19 ` Russell King - ARM Linux
2010-03-03 14:24 ` Pavel Machek
2010-03-03 14:38 ` Daniel Walker
2010-03-03 22:08 ` Nicolas Pitre
2010-03-03 22:27 ` Brian Swetland
2010-03-03 3:25 ` Bill Gatliff
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=a55d774e1003021538n5225b302ue1e77ea5e4f39fcc@mail.gmail.com \
--to=swetland@google.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).