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

Date:	Tue, 3 Jul 2007 04:01:20 -0500
From:	Kumar Gala <galak@...nel.crashing.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Linux Kernel Development <linux-kernel@...r.kernel.org>,
	linuxppc-dev list <linuxppc-dev@...abs.org>,
	Paul Mackerras <paulus@...ba.org>
Subject: How to handle patches that cross maintainers?

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.

Here's the diffstat to get a rough idea:

arch/powerpc/kernel/io.c                |   12 ++++++------
arch/powerpc/mm/hash_native_64.c        |    2 +-
arch/powerpc/mm/stab.c                  |    4 ++--
drivers/ide/pci/scc_pata.c              |    4 ++--
drivers/media/dvb/bt8xx/bt878.h         |    5 ++---
drivers/serial/cpm_uart/cpm_uart_core.c |    2 +-
include/asm-powerpc/system.h            |    2 +-
7 files changed, 15 insertions(+), 16 deletions(-)

Now, I've had this issue before w/o any good sense on how to handle it.

Suggestions?

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