linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [patch for 2.6.31] zaurus c3000 aka spitz: fix resume
Date: Thu, 10 Sep 2009 23:41:59 +0100	[thread overview]
Message-ID: <20090910224159.GA4360@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20090910191932.GA23721@elf.ucw.cz>

On Thu, Sep 10, 2009 at 09:19:32PM +0200, Pavel Machek wrote:
> On Wed 2009-09-09 19:23:40, Russell King - ARM Linux wrote:
> > On Wed, Sep 09, 2009 at 10:37:41PM +0800, Eric Miao wrote:
> > > On Wed, Sep 9, 2009 at 3:50 PM, Pavel Machek<pavel@ucw.cz> wrote:
> > > > Hi, Linus!
> > > >
> > > > Spitz resume was broken for year or likely two, and it would be very
> > > > nice to fix it for 2.6.31 release. One liner is below, and it really
> > > > can not harm. It already is in Eric's fix queue, so pulling that for
> > > > .31 should work, too.
> > > >
> > > 
> > > This should be sitting in rmk's git tree and I'm not sure if Russell
> > > has sent the pull request already.
> > 
> > It's just Pavel being his obnoxious impatient self...
> 
> Aha, Russell, being polite and helpful, as usual.
> 
> Only that, you know, you missed the deadline, so... perhaps I had
> reason to be impatient?

I missed the deadline because I was waiting on others to sort out telling
me whether a bugfix patch was actually correct, and then it took several
days and mails to get an attributation line out of them.  I finally got
that yesterday, and since I'm not doing kernel work (in fact, I'm hardly
in front of the computer at the moment) these things are going to _HAVE_
to wait until this weekend.

By agreement with Linus, I do not send pull requests more often than once
a week, absolute maximum.  So if I've something pending in the queue, I
hold off sending the queue until that issue is resolved.

Don't like it?  Tough.  This is the workflow that I've been forced into
by other flame wars.  It would be my personal preference to ensure that
fixes make their way in a timely manner into mainline, but due to that,
it's just not possible.

  reply	other threads:[~2009-09-10 22:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-09  7:50 [patch for 2.6.31] zaurus c3000 aka spitz: fix resume Pavel Machek
2009-09-09 14:37 ` Eric Miao
2009-09-09 18:23   ` Russell King - ARM Linux
2009-09-10 19:19     ` Pavel Machek
2009-09-10 22:41       ` Russell King - ARM Linux [this message]
2009-09-11  1:19         ` Eric Miao
2009-09-15 11:33           ` Pavel Machek
2009-09-09 14:49 ` Daniel Walker
2009-09-10  0:40   ` Eric Miao
2009-09-10 19:05     ` Pavel Machek

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=20090910224159.GA4360@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 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).