linux-kernel - Re: Linux 2.6.26-rc1

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20080506155723.df6bdcf9.sfr@canb.auug.org.au>
Date:	Tue, 6 May 2008 15:57:23 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	David Miller <davem@...emloft.net>, mingo@...e.hu, andi@...as.de,
	torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org,
	mchehab@...radead.org
Subject: Re: Linux 2.6.26-rc1

On Mon, 5 May 2008 17:16:57 -0700 Andrew Morton <akpm@...ux-foundation.org> wrote:
>
> On Mon, 05 May 2008 16:55:01 -0700 (PDT) David Miller <davem@...emloft.net> wrote:
> 
> As we discussed last week, I won't carry these patches because they're
> already upstream.  It turns out that "upstream" in this case is linux-next
> itself, which is an unexpected place for patches to be mastered.

Yeah, true.

> So I suggest that Stephen send patches such as this into Linus sooner
> rather than later.  Because nobody else will.

Right, I know that now :-)

> Well.  They _might_.  In this case Len could merge the patch in which case
> Stephen would drop it and the fix would dawdle around in the acpi tree for
> a while.

I guess that was my hope ...

> Ho hum, hopefully this isn't a common case.  Often Linus or I will just do
> a maintainer bypass on things like this, but my ability to do that is now
> much reduced because a) I can't merge the patch and b) when I _do_ try to
> do that, it's "huh, we already fixed it".

This is an uncommon case because normally I would just revert the
patch/tree that caused the problem.  In this case, the problem didn't
show up until after the linux-tree had been released so when the fix
patches turned up the next day I added them in the hope that someone else
would pick them up soon i.e. before they were needed in Linus' tree.  I
now know better.  :-)

> So... I hereby appoint Stephen random-build-fix-monkey.

Rats! :-)

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/

Content of type "application/pgp-signature" skipped