From: Christoph Hellwig <hch@lst.de>
To: Mike Rapoport <rppt@linux.ibm.com>
Cc: Christoph Hellwig <hch@lst.de>,
Andrew Morton <akpm@linux-foundation.org>,
Palmer Dabbelt <palmer@sifive.com>,
Richard Kuo <rkuo@codeaurora.org>,
linux-arch@vger.kernel.org, linux-hexagon@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH 0/4] provide a generic free_initmem implementation
Date: Mon, 18 Feb 2019 10:49:48 +0100 [thread overview]
Message-ID: <20190218094948.GA5892@lst.de> (raw)
In-Reply-To: <20190214183854.GA10795@rapoport-lnx>
On Thu, Feb 14, 2019 at 08:38:55PM +0200, Mike Rapoport wrote:
> On Thu, Feb 14, 2019 at 06:04:16PM +0100, Christoph Hellwig wrote:
> > This look fine to me, but I'm a little worried that as-is this will
> > just create conflicts with my series..
>
> I'll rebase on top of your patches once they are in. Or I can send both
> series as a single set.
> Preferences?
So far there wasn't really much a reason to rebase my series, hope
this gets picked up either by Andrew or Al (not sure what the right
place is). I think for now just rebase your series on top, we can
then figure out how to proceed.
prev parent reply other threads:[~2019-02-18 9:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 15:59 [PATCH 0/4] provide a generic free_initmem implementation Mike Rapoport
2019-02-14 15:59 ` [PATCH 1/4] init: " Mike Rapoport
2019-02-14 15:59 ` [PATCH 2/4] hexagon: switch over to generic free_initmem() Mike Rapoport
2019-02-14 15:59 ` [PATCH 3/4] init: free_initmem: poison freed init memory Mike Rapoport
2019-02-14 15:59 ` [PATCH 4/4] riscv: switch over to generic free_initmem() Mike Rapoport
2019-02-14 20:49 ` Palmer Dabbelt
2019-02-18 12:46 ` Souptick Joarder
2019-02-18 12:50 ` Souptick Joarder
2019-02-14 17:04 ` [PATCH 0/4] provide a generic free_initmem implementation Christoph Hellwig
2019-02-14 18:38 ` Mike Rapoport
2019-02-18 9:49 ` Christoph Hellwig [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=20190218094948.GA5892@lst.de \
--to=hch@lst.de \
--cc=akpm@linux-foundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@sifive.com \
--cc=rkuo@codeaurora.org \
--cc=rppt@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).