From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Paul Burton <paul.burton@mips.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Tony Luck <tony.luck@gmail.com>,
Mathieu Malaterre <malat@debian.org>,
linux-mm@kvack.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm/memblock: add missing include <linux/bootmem.h>
Date: Fri, 22 Jun 2018 09:34:21 +1000 [thread overview]
Message-ID: <20180622093421.6b060710@canb.auug.org.au> (raw)
In-Reply-To: <20180621180638.ahxpgzwrztopve55@pburton-laptop>
[-- Attachment #1: Type: text/plain, Size: 864 bytes --]
Hi Paul,
On Thu, 21 Jun 2018 11:06:38 -0700 Paul Burton <paul.burton@mips.com> wrote:
>
> I was expecting to see the original commit, then the revert, then
> perhaps a re-application of it but instead it looks like the commits
> from master are missing entirely after 25cf23d7a957 ("mm/memblock: print
> memblock_remove"). Maybe I'm missing something about the way the merges
> for linux-next are done..?
Andrew produces his mmotm quilt series and exports it to ozlabs.org
from where I fetch it and create the akpm-current and akpm branches in
linux-next (and merge them, obviously :-)). The mmotm quilt series has
not changed since Jun 15, I assume Andrew is still finalising it.
> In any case, could we get the problematic patch removed from linux-next?
I have removed it from my copy of mmotm for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2018-06-21 23:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 19:41 Mathieu Malaterre
2018-06-15 18:59 ` Tony Luck
2018-06-15 19:17 ` Andrew Morton
2018-06-15 22:26 ` Tony Luck
2018-06-15 23:32 ` Luck, Tony
2018-06-21 18:06 ` Paul Burton
2018-06-21 23:34 ` Stephen Rothwell [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=20180622093421.6b060710@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=malat@debian.org \
--cc=paul.burton@mips.com \
--cc=tony.luck@gmail.com \
/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