| 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: Mon, 13 Jun 2016 16:57:15 -0700 From: Kees Cook <keescook@...gle.com> To: Stephen Rothwell <sfr@...b.auug.org.au> Cc: Michal Marek <mmarek@...e.cz>, Linux-Next <linux-next@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>, Emese Revfy <re.emese@...il.com> Subject: Re: linux-next: duplicate patches in the kspp and kbuild trees On Mon, Jun 13, 2016 at 4:53 PM, Kees Cook <keescook@...gle.com> wrote: > On Mon, Jun 13, 2016 at 4:40 PM, Stephen Rothwell <sfr@...b.auug.org.au> wrote: >> Hi Kees, >> >> As of today, there are four duplicate patches (different commits) >> in the kspp and kbuild trees. >> >> Shared library support >> GCC plugin infrastructure >> Add Cyclomatic complexity GCC plugin >> Add sancov plugin >> >> are in both trees as different commits :-( They have been in the kbuild >> tree for a couple of days already. One of you should be merging the >> other's branch, or you both should be mergeing a common branch. >> >> Also, Kees, the versions in your tree do not have your Signed-off-by >> (but do have Michal's). > > Strange, I pulled these directly from linux-next. Michal had an > auto-responder saying he was going to be out-of-office, so I wanted to > make sure the !COMPILE_TEST fix got in. > > Sounds like I should merge the kbuild tree, rather than cherry-picking > from linux-next? I will adjust. I've done this merge correctly now and pushed a forced update on the kspp tree. -Kees > > Sorry for the confusion! > > -Kees > > -- > Kees Cook > Chrome OS & Brillo Security -- Kees Cook Chrome OS & Brillo Security
Powered by blists - more mailing lists