linux-kernel - Re: [PATCH][RFC] exception processing in early boot

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]

Date:	Wed, 30 Aug 2006 14:59:14 +0200
From:	Andi Kleen <ak@...e.de>
To:	Willy Tarreau <w@....eu>
Cc:	Riley@...liams.name, davej@...hat.com, pageexec@...email.hu,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH][RFC] exception processing in early boot


> Unfortunately, this situation is even more difficult for me, because it's
> getting very hard to track patches that get applied, rejected, modified or
> obsoleted, which is even more true when people don't always think about
> sending an ACK after the patch finally gets in. I already have a few pending
> patches in my queue waiting for an ACK that will have to be tracked if the
> persons do not respond, say, within one week. Otherwise I might simply lose
> them.

It shouldn't be that hard to check gitweb or git output occasionally
for the patches. You can probably even automate that.
 
> I think that the good method would be to :
>   - announce the patch
>   - find a volunteer to port it
>   - apply it once the volunteer agrees to handle it
> This way, no code gets lost because there's always someone to track it.

I can put that one into my tree for .19

-Andi

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