| 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
| ||
|
Date: Wed, 30 Nov 2011 14:32:42 -0800 From: Tony Lindgren <tony@...mide.com> To: Janusz Krzysztofik <jkrzyszt@....icnet.pl> Cc: Paul Walmsley <paul@...an.com>, linux-omap@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH 2a/5] Remove unsafe clock values from omap1_defconfig * Janusz Krzysztofik <jkrzyszt@....icnet.pl> [111128 13:26]: > > I'm not sure which of the patches you meant not ready for 3.2-rc. From > your comment I would conclude that only patch 3/5, which would really > break omap1_defconfig booting on some boards, is questionable, while you > posted this comment against patch 1/5, which I don't see how it could > break booting, including omap1_defconfig. Sorry for the delay in replying, yes you're right looks like it's allowing the rate changes currently that would break things in 3/5. > Anyway, I hope that the additional patch below is addressing all your > concerns. I'd rather not modify omap1_defconfig as a fix assuming that we'll be removing all those options anyways the next merge window together with your new patch. Can you please split your series into two: Fix(es) for the -rc cycle, then patches that can be left for the next merge window. Cheers, Tony -- 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