linux-kernel - Re: linux-next: manual merge of the akpm tree with lots of trees

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: <20171017232136.csbfpe4ieqnbqttr@sirena.org.uk>
Date:   Wed, 18 Oct 2017 00:21:36 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Andrew Morton <akpm@...ux-foundation.org>
Cc:     Linux-Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: manual merge of the akpm tree with lots of trees

On Tue, Oct 17, 2017 at 02:44:46PM -0700, Andrew Morton wrote:
> On Tue, 17 Oct 2017 20:44:19 +0100 Mark Brown <broonie@...nel.org> wrote:

> > Today's linux-next merge of (well, import of) the akpm tree got a
> > bunch of patches that were either applied or have conflicts with other
> > trees, apparmor and btrfs stand out.

> I don't know why that should be.

> I have a cleanly applying linux-next.patch today (you fixed something?)
> so I can do a fresh mmotm a couple hours from now.

I did the fetch that went in today in the early hours of the morning
(well, the computer did).  I did need to do fixups in the process of
building -next but I'm not sure if that's what you mean here.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)