From: Palmer Dabbelt <palmer@sifive.com>
To: logang@deltatee.com, linux-mm@kvack.org, akpm@linux-foundation.org
Cc: linux-arch@vger.kernel.org, aou@eecs.berkeley.edu,
Arnd Bergmann <arnd@arndb.de>,
linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org,
sbates@raithlin.com, linux-riscv@lists.infradead.org,
logang@deltatee.com, Christoph Hellwig <hch@lst.de>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/2] Introduce common code for risc-v sparsemem support
Date: Wed, 14 Nov 2018 10:06:24 -0800 (PST) [thread overview]
Message-ID: <mhng-dfc065e5-80c6-4a9d-b95b-95170df42969@palmer-si-x1c4> (raw)
Message-ID: <20181114180624.m4ujEVlg9e4nmKVWydtVThYErustunbRCwnOINRirH8@z> (raw)
In-Reply-To: <20181107205433.3875-1-logang@deltatee.com>
On Wed, 07 Nov 2018 12:54:31 PST (-0800), logang@deltatee.com wrote:
> These are the first two common patches in my series to introduce
> sparsemem support to RISC-V. The full series was posted last cycle
> here [1] and the latest version can be found here [2].
>
> As recommended by Palmer, I'd like to get the changes to common code
> merged and then I will pursue the cleanups in the individual arches (arm,
> arm64, and sh) as well as add the new feature to riscv.
>
> I would suggest we merge these two patches through Andrew's mm tree.
I haven't seen any review on this. It looks fine to me, but I'm not qualified
to review it as I don't really know anything about core MM stuff -- and I
certainly don't feel comfortable taking this through my tree.
I've To'd linux-mm, hopefully it just got lost in the shuffle during the merge
window.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2018-11-14 18:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 20:54 [PATCH v2 0/2] Introduce common code for risc-v sparsemem support Logan Gunthorpe
2018-11-07 20:54 ` Logan Gunthorpe
2018-11-07 20:54 ` [PATCH v2 1/2] mm: Introduce common STRUCT_PAGE_MAX_SHIFT define Logan Gunthorpe
2018-11-07 20:54 ` Logan Gunthorpe
2018-11-08 18:04 ` Catalin Marinas
2018-11-08 18:04 ` Catalin Marinas
2018-11-08 19:13 ` Ard Biesheuvel
2018-11-08 19:13 ` Ard Biesheuvel
2018-11-07 20:54 ` [PATCH v2 2/2] mm/sparse: add common helper to mark all memblocks present Logan Gunthorpe
2018-11-07 20:54 ` Logan Gunthorpe
2018-11-14 18:06 ` Palmer Dabbelt [this message]
2018-11-14 18:06 ` [PATCH v2 0/2] Introduce common code for risc-v sparsemem support Palmer Dabbelt
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=mhng-dfc065e5-80c6-4a9d-b95b-95170df42969@palmer-si-x1c4 \
--to=palmer@sifive.com \
--cc=akpm@linux-foundation.org \
--cc=aou@eecs.berkeley.edu \
--cc=arnd@arndb.de \
--cc=hch@lst.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-sh@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=sbates@raithlin.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).