linux-kernel - Re: [git patches] parisc for 2.6.32

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] [day] [month] [year] [list]

Message-ID: <4ACBAE49.9020903@gmx.de>
Date:	Tue, 06 Oct 2009 22:53:29 +0200
From:	Helge Deller <deller@....de>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
CC:	kyle@...artin.ca, linux-kernel@...r.kernel.org,
	linux-parisc@...r.kernel.org
Subject: Re: [git patches] parisc for 2.6.32

Hi Linus,

On 10/06/2009 07:40 PM, Linus Torvalds wrote:
> On Tue, 6 Oct 2009, Kyle McMartin wrote:
>> Mostly fixes, except for the tracehook stuff...
>
> I don't see how this can be fixes, since I can't recall any parisc pulls
> during the merge window.

Yes, sadly it was not in time.
And of course it's no excuse, that you didn't received a real pull-request,
even after Kyle asked for feedback for his tree with his mail on LKML and
parisc-list on 2009-09-28:
http://www.pubbs.net/kernel/200909/123965/

> So now you come in after the merge window has been closed for over a week,
> and want to do a parisc merge?
>
> Tell me why I should take this. Tell me why I shouldn't just wait until
> the next merge window (or rather "_you_ should have waited").

This patch really only touches parisc-specific files and it includes
important fixes without which the parisc kernel won't even compile and link.
So, it would help us parisc-porters a lot if you could do an exception and
still pull from Kyle's tree, even after this merge window has been closed.
At least, it would make me personally very happy...

Helge
--
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/