From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1955722AbdDZFre (ORCPT ); Wed, 26 Apr 2017 01:47:34 -0400 Received: from ozlabs.org ([103.22.144.67]:33613 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1949938AbdDZFrZ (ORCPT ); Wed, 26 Apr 2017 01:47:25 -0400 Date: Wed, 26 Apr 2017 15:47:22 +1000 From: Stephen Rothwell To: "Martin K. Petersen" , Jens Axboe Cc: Linux-Next Mailing List , Linux Kernel Mailing List , Damien Le Moal , Christoph Hellwig Subject: linux-next: manual merge of the scsi-mkp tree with the block tree Message-ID: <20170426154722.757ba483@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi all, Today's linux-next merge of the scsi-mkp tree got a conflict in: drivers/scsi/sd.c between commit: 81d926e8b552 ("sd: split sd_setup_discard_cmnd") from the block tree and commit: 7529fbb0080d ("scsi: sd: Fix function descriptions") from the scsi-mkp tree. I fixed it up (I just used the former version) 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