From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756413AbcECUDq (ORCPT ); Tue, 3 May 2016 16:03:46 -0400 Received: from mail-pa0-f49.google.com ([209.85.220.49]:34502 "EHLO mail-pa0-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756342AbcECUDo (ORCPT ); Tue, 3 May 2016 16:03:44 -0400 Subject: Re: linux-next: manual merge of the block tree with Linus' tree To: Stephen Rothwell References: <20160503142552.1c5e1d83@canb.auug.org.au> Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Keith Busch , Christoph Hellwig From: Jens Axboe Message-ID: <5729041D.7070707@kernel.dk> Date: Tue, 3 May 2016 14:03:41 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: <20160503142552.1c5e1d83@canb.auug.org.au> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 05/02/2016 10:25 PM, Stephen Rothwell wrote: > Hi Jens, > > Today's linux-next merge of the block tree got a conflict in: > > drivers/nvme/host/pci.c > > between commit: > > 9bf2b972afea ("NVMe: Fix reset/remove race") > > from Linus' tree and commit: > > bb8d261e0888 ("nvme: introduce a controller state machine") > > from the block tree. > > I fixed it up (I think - see below) 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. There's a proper fixup in my for-next now, so you should be able to drop this one. -- Jens Axboe