| 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
| ||
|
Message-Id: <20061004211259.8274db49.akpm@osdl.org> Date: Wed, 4 Oct 2006 21:12:59 -0700 From: Andrew Morton <akpm@...l.org> To: Len Brown <lenb@...nel.org> Cc: Len Brown <len.brown@...el.com>, Jan Engelhardt <jengelh@...ux01.gwdg.de>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, ACPI List <linux-acpi@...r.kernel.org> Subject: Re: [PATCH] Cast removal On Wed, 4 Oct 2006 23:56:02 -0400 Len Brown <len.brown@...el.com> wrote: > I'm okay applying this patch it touches the linux-specific > drivers/acpi/* files only, no ACPICA files. Why? Would it help if it was split into two? How do mortals distinguish ACPICA files from Linux files? > But I don't know if Linus will want changes like this post -rc1. > It might be a pain to have in the tree all the way to 2.6.20 opens b/c > it is sure to cause merge conflicts Should be OK - the acpi tree is very slow-changing at present. Or did you have big changes planned? Or I can maintain it externally along with the 10-20 other acpi patches I seem to be regularly stuck with (hint ;) > -- and at the end of the day > the benefit of this patch is what? A few less characters in the source... > yes, cleanups are a pain, and we do a lot of them. And we merge just about all of them. But I think it's best in the long run; and we are in this for the long run. - 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/
Powered by blists - more mailing lists