public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Kees Cook <keescook@google•com>, Michal Marek <mmarek@suse•cz>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
	Emese Revfy <re.emese@gmail•com>
Subject: linux-next: duplicate patches in the kspp and kbuild trees
Date: Tue, 14 Jun 2016 09:40:19 +1000	[thread overview]
Message-ID: <20160614094019.14fac372@canb.auug.org.au> (raw)

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).

-- 
Cheers,
Stephen Rothwell

             reply	other threads:[~2016-06-13 23:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-13 23:40 Stephen Rothwell [this message]
2016-06-13 23:53 ` linux-next: duplicate patches in the kspp and kbuild trees Kees Cook
2016-06-13 23:57   ` Kees Cook
2016-06-14  4:32     ` Stephen Rothwell
2016-06-14 13:01       ` Michal Marek
2016-06-14 14:13         ` Stephen Rothwell
2016-06-14 16:39           ` Kees Cook
2016-07-26 22:19             ` Michal Marek
2016-07-26 23:09               ` Kees Cook
2016-07-27  7:52                 ` Michal Marek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160614094019.14fac372@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=keescook@google$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=mmarek@suse$(echo .)cz \
    --cc=re.emese@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox