From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752370AbdFMEdF (ORCPT ); Tue, 13 Jun 2017 00:33:05 -0400 Received: from ozlabs.org ([103.22.144.67]:45783 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751996AbdFMEdD (ORCPT ); Tue, 13 Jun 2017 00:33:03 -0400 Date: Tue, 13 Jun 2017 14:33:01 +1000 From: Stephen Rothwell To: Shaohua Li , Jens Axboe Cc: Linux-Next Mailing List , Linux Kernel Mailing List , Christoph Hellwig , Guoqing Jiang Subject: linux-next: manual merge of the md tree with the block tree Message-ID: <20170613143301.0c4a80f9@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 Shaohua, Today's linux-next merge of the md tree got a conflict in: drivers/md/raid5.c between commit: 4e4cbee93d56 ("block: switch bios to blk_status_t") from the block tree and commit: 66a8066d55fd ("md: simplify code with bio_io_error") from the md tree. I fixed it up (the latter removed code updated by the former) 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