From: Mark Brown <broonie@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: manual merge of the akpm tree with lots of trees
Date: Wed, 18 Oct 2017 00:21:36 +0100 [thread overview]
Message-ID: <20171017232136.csbfpe4ieqnbqttr@sirena.org.uk> (raw)
In-Reply-To: <20171017144446.3beac671d798906122a21e38@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 691 bytes --]
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@kernel.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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2017-10-17 23:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 19:44 linux-next: manual merge of the akpm tree with lots of trees Mark Brown
2017-10-17 21:44 ` Andrew Morton
2017-10-17 23:21 ` Mark Brown [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171017232136.csbfpe4ieqnbqttr@sirena.org.uk \
--to=broonie@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox