From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934961AbdJQVot (ORCPT ); Tue, 17 Oct 2017 17:44:49 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:50482 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754359AbdJQVos (ORCPT ); Tue, 17 Oct 2017 17:44:48 -0400 Date: Tue, 17 Oct 2017 14:44:46 -0700 From: Andrew Morton To: Mark Brown Cc: Linux-Next Mailing List , Linux Kernel Mailing List Subject: Re: linux-next: manual merge of the akpm tree with lots of trees Message-Id: <20171017144446.3beac671d798906122a21e38@linux-foundation.org> In-Reply-To: <20171017194419.73s7cro4bvkaoukh@sirena.co.uk> References: <20171017194419.73s7cro4bvkaoukh@sirena.co.uk> X-Mailer: Sylpheed 3.4.1 (GTK+ 2.24.23; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 17 Oct 2017 20:44:19 +0100 Mark Brown 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.