From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756788AbcLADE7 (ORCPT ); Wed, 30 Nov 2016 22:04:59 -0500 Received: from mail-pf0-f170.google.com ([209.85.192.170]:36292 "EHLO mail-pf0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755305AbcLADE5 (ORCPT ); Wed, 30 Nov 2016 22:04:57 -0500 Subject: Re: linux-next: build failure after merge of the block tree To: Stephen Rothwell References: <20161201135517.273c9a4d@canb.auug.org.au> <20161201140243.2554a006@canb.auug.org.au> Cc: David Chinner , xfs@oss.sgi.com, linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Christoph Hellwig From: Jens Axboe Message-ID: Date: Wed, 30 Nov 2016 20:04:53 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <20161201140243.2554a006@canb.auug.org.au> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11/30/2016 08:02 PM, Stephen Rothwell wrote: > Hi Jens, > > On Wed, 30 Nov 2016 20:00:36 -0700 Jens Axboe wrote: >> >> On 11/30/2016 07:55 PM, Stephen Rothwell wrote: >>> >>> I love APIs changing :-( >> >> It's a necessary evil... > > Yeah > >> This could have been avoided with the XFS tree pulling in the block >> changes, but that obviously has other implications. Something to watch >> for when the XFS tree is sent in for the merge window, however. > > Indeed. Or the block tree, which ever comes last. Sure, but I usually try and push in the first few days since other trees depend on mine. So it's more likely that the XFS tree will run into the issue. -- Jens Axboe