All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
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 11:18:00 +0100	[thread overview]
Message-ID: <20100303101759.GA10499@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <20100303100847.GA30607@n2100.arm.linux.org.uk>


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"?

Note that board_dream.c is already in the tree.

> Yes, go back and read the fucking thread properly Pavel.  Daniel
> explicitly sent his messages TO me and ASKED me for this.
> 
> Daniel had my suggestions on my first reply in this thread, and his
> follow up to that indicated he wanted something firmer - he wanted
> a decision _FROM ME_ on which way to go.  That's precisely what he
> got.
> 
> What you're actually trying to say is that you don't like me and you
> certainly don't like me making any kind of decision.  Get over it, or
> find some other project to infiltrate and infest with your idiotic
> attitude.

Stop putting words in my mouth. And start to behave.
									Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

WARNING: multiple messages have this Message-ID (diff)
From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: board/device file names, and machine names
Date: Wed, 3 Mar 2010 11:18:00 +0100	[thread overview]
Message-ID: <20100303101759.GA10499@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <20100303100847.GA30607@n2100.arm.linux.org.uk>


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"?

Note that board_dream.c is already in the tree.

> Yes, go back and read the fucking thread properly Pavel.  Daniel
> explicitly sent his messages TO me and ASKED me for this.
> 
> Daniel had my suggestions on my first reply in this thread, and his
> follow up to that indicated he wanted something firmer - he wanted
> a decision _FROM ME_ on which way to go.  That's precisely what he
> got.
> 
> What you're actually trying to say is that you don't like me and you
> certainly don't like me making any kind of decision.  Get over it, or
> find some other project to infiltrate and infest with your idiotic
> attitude.

Stop putting words in my mouth. And start to behave.
									Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2010-03-03 10:18 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 [this message]
2010-03-03 10:18                 ` Pavel Machek
2010-03-03 10:19                 ` Russell King - ARM Linux
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=20100303101759.GA10499@atrey.karlin.mff.cuni.cz \
    --to=pavel@ucw.cz \
    --cc=dwalker@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=swetland@google.com \
    /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.