From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933411AbdKPEzh (ORCPT ); Wed, 15 Nov 2017 23:55:37 -0500 Received: from LGEAMRELO13.lge.com ([156.147.23.53]:54048 "EHLO lgeamrelo13.lge.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933311AbdKPEz3 (ORCPT ); Wed, 15 Nov 2017 23:55:29 -0500 X-Original-SENDERIP: 156.147.1.151 X-Original-MAILFROM: minchan@kernel.org X-Original-SENDERIP: 10.177.220.163 X-Original-MAILFROM: minchan@kernel.org Date: Thu, 16 Nov 2017 13:55:26 +0900 From: Minchan Kim To: Stephen Rothwell Cc: Andrew Morton , Dan Williams , Linux-Next Mailing List , Linux Kernel Mailing List Subject: Re: linux-next: manual merge of the akpm-current tree with the nvdimm tree Message-ID: <20171116045526.GA13115@bbox> References: <20171116141627.65df4240@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171116141627.65df4240@canb.auug.org.au> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Stephen, On Thu, Nov 16, 2017 at 02:16:27PM +1100, Stephen Rothwell wrote: > Hi Andrew, > > Today's linux-next merge of the akpm-current tree got a conflict in: > > drivers/block/brd.c > > between commit: > > 7a862fbbdec6 ("brd: remove dax support") > > from the nvdimm tree and commit: > > f8ace3501d00 ("bdi: introduce BDI_CAP_SYNCHRONOUS_IO") > > from the akpm-current tree. > > I fixed it up (see below) and can carry the fix as necessary. This It's good for me. Thanks.