lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Tue, 15 Sep 2009 13:33:47 +0200
From:	Pavel Machek <pavel@....cz>
To:	Eric Miao <eric.y.miao@...il.com>
Cc:	Russell King - ARM Linux <linux@....linux.org.uk>,
	rpurdie@...ys.net, lenz@...wisc.edu,
	kernel list <linux-kernel@...r.kernel.org>,
	Dirk@...er-online.de, arminlitzel@....de,
	Cyril Hrubis <metan@....cz>, thommycheck@...il.com,
	linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
	dbaryshkov@...il.com, omegamoon@...il.com, utx@...guin.cz,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [patch for 2.6.31] zaurus c3000 aka spitz: fix resume

On Fri 2009-09-11 09:19:19, Eric Miao wrote:
> On Fri, Sep 11, 2009 at 6:41 AM, Russell King - ARM Linux
> <linux@....linux.org.uk> wrote:
> > 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@....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.
> >
> 
> Pavel,
> 
> It is still possible to get this into the stable release so take easy.

Ok, so can you (or Russell?) add cc: stable@...nel.org header so that
stable is notified when patch is merged?
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists