linux-kernel - Re: linux-next: build failure after merge of the gpio tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CACRpkdZ+tvhq4X19LTb9tjE4v0J1qaTh-EtVOER3GmQw5xHN0w@mail.gmail.com>
Date:   Fri, 3 Nov 2017 22:40:23 +0100
From:   Linus Walleij <linus.walleij@...aro.org>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>,
        "H. Peter Anvin" <hpa@...or.com>,
        Peter Zijlstra <peterz@...radead.org>,
        Linux-Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Masahiro Yamada <yamada.masahiro@...ionext.com>
Subject: Re: linux-next: build failure after merge of the gpio tree

On Fri, Nov 3, 2017 at 9:13 AM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi Linus,
>
> On Fri, 3 Nov 2017 08:50:31 +0100 Linus Walleij <linus.walleij@...aro.org> 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