Re: linux-next: manual merge of the pci tree with Linus' tree

From	Bjorn Helgaas <helgaas@kernel.org>
Newsgroups	linux.kernel
Subject	Re: linux-next: manual merge of the pci tree with Linus' tree
Date	2016-06-23 18:50 +0200
Message-ID	<rNfZg-4gz-11@gated-at.bofh.it> (permalink)
References	<rN1Wi-2Yp-5@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Thu, Jun 23, 2016 at 11:44:29AM +1000, Stephen Rothwell wrote:
> Hi Bjorn,
> 
> Today's linux-next merge of the pci tree got a conflict in:
> 
>   drivers/nvme/host/pci.c
> 
> between commit:
> 
>   edb50a5403d2 ("NVMe: Only release requested regions")
> 
> from Linus' tree and commit:
> 
>   a1f447b35b72 ("NVMe: Use pci_(request|release)_mem_regions")
> 
> from the pci tree.
> 
> I fixed it up (I just used the pci tree version of this file) 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.

Thanks for the heads-up.  I think using the pci tree version is the
correct resolution.

Bjorn

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

Thread

linux-next: manual merge of the pci tree with Linus' tree Stephen Rothwell <sfr@canb.auug.org.au> - 2016-06-23 03:50 +0200
  Re: linux-next: manual merge of the pci tree with Linus' tree Bjorn Helgaas <helgaas@kernel.org> - 2016-06-23 18:50 +0200

csiph-web