All of lore.kernel.org
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: board/device file names, and machine names
Date: Wed, 3 Mar 2010 10:19:57 +0000	[thread overview]
Message-ID: <20100303101957.GA9848@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20100303101759.GA10499@atrey.karlin.mff.cuni.cz>

On Wed, Mar 03, 2010 at 11:18:00AM +0100, Pavel Machek wrote:
> 
> Hi!
> 
> > > > > > Given the amount of discussion there's already been, I'm going to come
> > > > > > down hard on this issue to kill the discussion.
> 
> > > So... dwalker is maintainer of arch-msm, and does not like the
> > > codenames. Then you come, and just because are maintainer of arm,
> > > override the decision, without even notifying l-k?
> > 
> > So you don't think that Daniel, who was *explicitly* asking for my
> > suggestions and opinions, is entitled to a clear and straight
> > answer?
> 
> When someone asks for your suggestions, you can "go down hard on this
> issue"?

It's clear that all you want to have is an argument.  This ends here.

WARNING: multiple messages have this Message-ID (diff)
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Pavel Machek <pavel@ucw.cz>
Cc: Daniel Walker <dwalker@codeaurora.org>,
	linux-arm-msm@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, swetland@google.com,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: board/device file names, and machine names
Date: Wed, 3 Mar 2010 10:19:57 +0000	[thread overview]
Message-ID: <20100303101957.GA9848@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20100303101759.GA10499@atrey.karlin.mff.cuni.cz>

On Wed, Mar 03, 2010 at 11:18:00AM +0100, Pavel Machek wrote:
> 
> Hi!
> 
> > > > > > Given the amount of discussion there's already been, I'm going to come
> > > > > > down hard on this issue to kill the discussion.
> 
> > > So... dwalker is maintainer of arch-msm, and does not like the
> > > codenames. Then you come, and just because are maintainer of arm,
> > > override the decision, without even notifying l-k?
> > 
> > So you don't think that Daniel, who was *explicitly* asking for my
> > suggestions and opinions, is entitled to a clear and straight
> > answer?
> 
> When someone asks for your suggestions, you can "go down hard on this
> issue"?

It's clear that all you want to have is an argument.  This ends here.

  reply	other threads:[~2010-03-03 10:19 UTC|newest]

Thread overview: 31+ 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
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:18                 ` Pavel Machek
2010-03-03 10:19                 ` Russell King - ARM Linux [this message]
2010-03-03 10:19                   ` Russell King - ARM Linux
2010-03-03 14:24                   ` Pavel Machek
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=20100303101957.GA9848@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.