linux-next: manual merge of the kbuild tree with the input-current tree

Path	csiph.com!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod
From	Stephen Rothwell <sfr@canb.auug.org.au>
Newsgroups	linux.kernel
Subject	linux-next: manual merge of the kbuild tree with the input-current tree
Date	Tue, 28 Mar 2017 01:00:02 +0200
Message-ID	<tpLMe-6Ms-13@gated-at.bofh.it> (permalink)
X-Original-To	Masahiro Yamada <yamada.masahiro@socionext.com>, Dmitry Torokhov <dmitry.torokhov@gmail.com>
Dkim-Signature	v=1; a=rsa-sha256; c=relaxed/simple; d=canb.auug.org.au; s=201702; t=1490655333; bh=VI8hNGrylak/6yQ8q2NhJXTc70AeTeOXPSgNtd/nYXc=; h=Date:From:To:Cc:Subject:From; b=Rjpq9IZtcRCJMt1cUAHr+ZtB7+aJA4ZE5GdXY6M40ZLgvqPgKmJvZveA4Xzc+eefU ViaRlS2h/WueFV990+4Z+XBUhAB48FTdBnCfONd65EM/Dy+mBCR4rTir7gQ0u2LPEW KRiOMdeO9XEcgGj1C/oc65820NiIhJDD5+NCk84Thp2lta4JoIKvVpw6vy46Prw0KY qjeW/Cu/BFBs0Tn44IXCBNp0oykaw10Z1TlpG/d9PdqLjf+dqHM6qxp3vbpWc5kcBr /tvTyYwjDbJGnHn1tGGKsvgv5pTiSc6UrhA2nT4vHmu0UfOZa+xuQpYMdQeAsCfIIL C0/itS2tE6wxA==
MIME-Version	1.0
Content-Type	text/plain; charset=US-ASCII
Content-Transfer-Encoding	7bit
Sender	robomod@news.nic.it
List-ID	<linux-kernel.vger.kernel.org>
X-Mailing-List	linux-kernel@vger.kernel.org
Approved	robomod@news.nic.it
Lines	26
Organization	linux.* mail to news gateway
X-Original-Cc	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Nicolas Dichtel <nicolas.dichtel@6wind.com>, Naohiro Aota <naota@elisp.net>
X-Original-Date	Tue, 28 Mar 2017 09:55:32 +1100
X-Original-Message-ID	<20170328095532.04abad61@canb.auug.org.au>
X-Original-Sender	linux-kernel-owner@vger.kernel.org
Xref	csiph.com linux.kernel:1610146

Show key headers only | View raw

Hi Masahiro,

Today's linux-next merge of the kbuild tree got a conflict in:

  include/uapi/linux/Kbuild

between commit:

  5659495a7a14 ("uapi: add missing install of userio.h")

from the input-current tree and commit:

  65017bab8a9e ("uapi: export all headers under uapi directories")

from the kbuild tree.

I fixed it up (the latter supercedes the former, so I just used it) and
can carry the fix as necessary. This is now fixed as far as linux-next
is concerned, but any non trivial conflicts should be mentioned to your
upstream maintainer when your tree is submitted for merging.  You may
also want to consider cooperating with the maintainer of the conflicting
tree to minimise any particularly complex conflicts.

-- 
Cheers,
Stephen Rothwell

Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

linux-next: manual merge of the kbuild tree with the input-current  tree Stephen Rothwell <sfr@canb.auug.org.au> - 2017-03-28 01:00 +0200
  Re: linux-next: manual merge of the kbuild tree with the  input-current tree Masahiro Yamada <yamada.masahiro@socionext.com> - 2017-03-28 03:00 +0200

csiph-web