Re: linux-next: duplicate patches in the kspp and kbuild trees

2016-07-27 Thread Michal Marek
On 2016-07-27 01:09, Kees Cook wrote: > On Tue, Jul 26, 2016 at 3:19 PM, Michal Marek wrote: >> Dne 14.6.2016 v 18:39 Kees Cook napsal(a): >>> On Tue, Jun 14, 2016 at 7:13 AM, Stephen Rothwell >>> wrote: Hi Michal, On Tue, 14 Jun 2016 15:01:42 +0200 Michal Marek wrote: >

Re: linux-next: duplicate patches in the kspp and kbuild trees

2016-07-26 Thread Kees Cook
On Tue, Jul 26, 2016 at 3:19 PM, Michal Marek wrote: > Dne 14.6.2016 v 18:39 Kees Cook napsal(a): >> On Tue, Jun 14, 2016 at 7:13 AM, Stephen Rothwell >> wrote: >>> Hi Michal, >>> >>> On Tue, 14 Jun 2016 15:01:42 +0200 Michal Marek wrote: I won't :). Kees, are you going to keep the pa

Re: linux-next: duplicate patches in the kspp and kbuild trees

2016-07-26 Thread Michal Marek
Dne 14.6.2016 v 18:39 Kees Cook napsal(a): > On Tue, Jun 14, 2016 at 7:13 AM, Stephen Rothwell > wrote: >> Hi Michal, >> >> On Tue, 14 Jun 2016 15:01:42 +0200 Michal Marek wrote: >>> >>> I won't :). Kees, are you going to keep the patch in your tree and send >>> it to Linus once kbuild is in? Or

Re: linux-next: duplicate patches in the kspp and kbuild trees

2016-06-14 Thread Kees Cook
On Tue, Jun 14, 2016 at 7:13 AM, Stephen Rothwell wrote: > Hi Michal, > > On Tue, 14 Jun 2016 15:01:42 +0200 Michal Marek wrote: >> >> I won't :). Kees, are you going to keep the patch in your tree and send >> it to Linus once kbuild is in? Or shall I take it (which would >> temporarily result in

Re: linux-next: duplicate patches in the kspp and kbuild trees

2016-06-14 Thread Stephen Rothwell
Hi Michal, On Tue, 14 Jun 2016 15:01:42 +0200 Michal Marek wrote: > > I won't :). Kees, are you going to keep the patch in your tree and send > it to Linus once kbuild is in? Or shall I take it (which would > temporarily result in another duplication...). Or Kees could send you a pull request ..

Re: linux-next: duplicate patches in the kspp and kbuild trees

2016-06-14 Thread Michal Marek
On 2016-06-14 06:32, Stephen Rothwell wrote: > Hi Kees, > > On Mon, 13 Jun 2016 16:57:15 -0700 Kees Cook wrote: >> >> On Mon, Jun 13, 2016 at 4:53 PM, Kees Cook wrote: >>> >>> Strange, I pulled these directly from linux-next. Michal had an >>> auto-responder saying he was going to be out-of-offi

Re: linux-next: duplicate patches in the kspp and kbuild trees

2016-06-13 Thread Stephen Rothwell
Hi Kees, On Mon, 13 Jun 2016 16:57:15 -0700 Kees Cook wrote: > > On Mon, Jun 13, 2016 at 4:53 PM, Kees Cook wrote: > > > > 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 fi

Re: linux-next: duplicate patches in the kspp and kbuild trees

2016-06-13 Thread Kees Cook
On Mon, Jun 13, 2016 at 4:53 PM, Kees Cook wrote: > On Mon, Jun 13, 2016 at 4:40 PM, Stephen Rothwell > 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 >> A

Re: linux-next: duplicate patches in the kspp and kbuild trees

2016-06-13 Thread Kees Cook
On Mon, Jun 13, 2016 at 4:40 PM, Stephen Rothwell 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 > > ar

linux-next: duplicate patches in the kspp and kbuild trees

2016-06-13 Thread Stephen Rothwell
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 f