From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754253AbdKCVk0 (ORCPT ); Fri, 3 Nov 2017 17:40:26 -0400 Received: from mail-io0-f176.google.com ([209.85.223.176]:51307 "EHLO mail-io0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750772AbdKCVkY (ORCPT ); Fri, 3 Nov 2017 17:40:24 -0400 X-Google-Smtp-Source: ABhQp+TVtNbk/N8OKzLcluIP0XVWDMZdRr/ZV2vTtKYbeSGb3IbUpg2pTbWO7RkpePtqL4xJ9/roCvijALgZUToZsVA= MIME-Version: 1.0 In-Reply-To: <20171103191316.27a28dd9@canb.auug.org.au> References: <20171102162038.339466ef@canb.auug.org.au> <20171103191316.27a28dd9@canb.auug.org.au> From: Linus Walleij Date: Fri, 3 Nov 2017 22:40:23 +0100 Message-ID: Subject: Re: linux-next: build failure after merge of the gpio tree To: Stephen Rothwell Cc: Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Peter Zijlstra , Linux-Next Mailing List , Linux Kernel Mailing List , Masahiro Yamada Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Nov 3, 2017 at 9:13 AM, Stephen Rothwell wrote: > Hi Linus, > > On Fri, 3 Nov 2017 08:50:31 +0100 Linus Walleij wrote: >> >> I applied this patch to the GPIO tree, I guess it is the right thing >> to do at this point. > > Umm, you can't really validly apply my merge fix patch to the gpio tree > without merging in part of the tip tree (it will generate, at least, > warnings in your build testing of your tree) ... OK I take it out again... >> I suspect the IRQ infrastructure will be pulled to Torvald's tree >> first anyway. > > You just need to let Linus know that this update is require (maybe > provide him with my merge fix patch) when you send your pull request. OK I will try to do that. Yours, Linus Walleij