linux-kernel - Re: How to handle patches that cross maintainers?

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:	Tue, 3 Jul 2007 16:13:51 +0200
From:	Christoph Hellwig <hch@....de>
To:	Kumar Gala <galak@...nel.crashing.org>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linuxppc-dev list <linuxppc-dev@...abs.org>,
	Paul Mackerras <paulus@...ba.org>,
	Linux Kernel Development <linux-kernel@...r.kernel.org>
Subject: Re: How to handle patches that cross maintainers?

On Tue, Jul 03, 2007 at 04:01:20AM -0500, Kumar Gala wrote:
> Andrew,
> 
> I was hoping to get your input on how to handle patches that cross  
> maintainers.  I've got a patch that is pretty PPC specific, but  
> happens to touch some drivers as well.

I think the real question is why the heck does it touch those drivers?
:)

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