linux-kernel - Re: linux-next: build failure after merge of the akpm-current 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] [day] [month] [year] [list]

Message-ID: <CAPcyv4ifFfASkdSG7cjT7FdVC5x8hxFEnMhHpjnGPz_pkMYd9Q@mail.gmail.com>
Date:   Wed, 21 Oct 2020 15:57:46 -0700
From:   Dan Williams <dan.j.williams@...el.com>
To:     Miklos Szeredi <miklos@...redi.hu>
Cc:     "sfr@...b.auug.org.au" <sfr@...b.auug.org.au>,
        "akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
        "jgross@...e.com" <jgross@...e.com>,
        "bo.liu@...ux.alibaba.com" <bo.liu@...ux.alibaba.com>,
        "linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
        "stefanha@...hat.com" <stefanha@...hat.com>,
        "roger.pau@...rix.com" <roger.pau@...rix.com>,
        "vgoyal@...hat.com" <vgoyal@...hat.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "dgilbert@...hat.com" <dgilbert@...hat.com>,
        "Boeuf, Sebastien" <sebastien.boeuf@...el.com>
Subject: Re: linux-next: build failure after merge of the akpm-current tree

On Fri, Oct 16, 2020 at 12:45 PM Miklos Szeredi <miklos@...redi.hu> wrote:
[..]
> > This is broken... it needs to be converted to 'struct range'. I'll take
> > care of that when I respin the series. Sorry for the thrash it seems
> > this is a new memremap_pages() user since the conversion patches
> > landed.
>
> Hi Dan,
>
> I'd like to send this upstream and this conflict needs to be dealt
> with some way or another.   Can you send the correct fixup against
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git#for-next

Sorry, I just circled back to this and found your for-next branch is
already merged. The resolution looks good. Apologies for not taking a
look earlier.