linux-kernel - Re: XArray -next inclusion request

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: <20180704225431.GA16309@bombadil.infradead.org>
Date:   Wed, 4 Jul 2018 15:54:31 -0700
From:   Matthew Wilcox <willy@...radead.org>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     linux-mm@...ck.org, linux-fsdevel@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: XArray -next inclusion request

On Sun, Jun 17, 2018 at 01:41:04PM +1000, Stephen Rothwell wrote:
> Hi Willy,
> 
> On Sat, 16 Jun 2018 19:15:22 -0700 Matthew Wilcox <willy@...radead.org> wrote:
> >
> > Please add
> > 
> > git://git.infradead.org/users/willy/linux-dax.git xarray
> > 
> > to linux-next.  It is based on -rc1.  You will find some conflicts
> > against Dan's current patches to DAX; these are all resolved correctly
> > in the xarray-20180615 branch which is based on next-20180615.
> 
> Added from tomorrow.

Thanks!  I have some additional patches for the IDA that I'd like to
send to Linus as a separate pull request.  Unfortunately, they conflict with
the XArray patches, so I've done them as a separate branch in the same tree:

git://git.infradead.org/users/willy/linux-dax.git ida

Would you prefer to add them as a separate branch to linux-next (to be
pulled after xarray), or would you prefer to replace the xarray pull
with the ida pull?  Either way, you'll get the same commits as the ida
branch is based off the xarray branch.