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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 17 Apr 2021 12:24:03 +0800 From: David Gow <davidgow@...gle.com> To: Matthieu Baerts <matthieu.baerts@...sares.net> Cc: Nico Pache <npache@...hat.com>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Brendan Higgins <brendanhiggins@...gle.com>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, linux-ext4@...r.kernel.org, Networking <netdev@...r.kernel.org>, rafael@...nel.org, linux-m68k@...ts.linux-m68k.org, Geert Uytterhoeven <geert@...ux-m68k.org>, "Theodore Ts'o" <tytso@....edu>, mathew.j.martineau@...ux.intel.com, davem@...emloft.net, Mark Brown <broonie@...nel.org>, Shuah Khan <skhan@...uxfoundation.org>, mptcp@...ts.linux.dev Subject: Re: [PATCH v2 5/6] kunit: mptcp: adhear to KUNIT formatting standard Hi Matt, > Like patch 1/6, I can apply it in MPTCP tree and send it later to > net-next with other patches. > Except if you guys prefer to apply it in KUnit tree and send it to > linux-next? Given 1/6 is going to net-next, it makes sense to send this out that way too, then, IMHO. The only slight concern I have is that the m68k test config patch in the series will get split from the others, but that should resolve itself when they pick up the last patch. At the very least, this shouldn't cause any conflicts with anything we're doing in the KUnit tree. Cheers, -- David
Powered by blists - more mailing lists