From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andrew Morton <akpm@linux-foundation.org>
Subject: Re: linux-next: manual merge of the akpm tree with lots of trees
Date: Tue, 17 Oct 2017 14:44:46 -0700
Message-ID: <20171017144446.3beac671d798906122a21e38@linux-foundation.org>
References: <20171017194419.73s7cro4bvkaoukh@sirena.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Return-path: <linux-kernel-owner@vger.kernel.org>
In-Reply-To: <20171017194419.73s7cro4bvkaoukh@sirena.co.uk>
Sender: linux-kernel-owner@vger.kernel.org
To: Mark Brown <broonie@kernel.org>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
List-Id: linux-next.vger.kernel.org

On Tue, 17 Oct 2017 20:44:19 +0100 Mark Brown <broonie@kernel.org> wrote:

> Hi Andrew,
> 
> 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.