From: Palmer Dabbelt <palmer@sifive.com>
To: logang@deltatee.com
Cc: robh@kernel.org, dalias@libc.org, ysato@users.sourceforge.jp,
dan.j.williams@intel.com, linux-kernel@vger.kernel.org,
sbates@raithlin.com, Christoph Hellwig <hch@infradead.org>,
linux-riscv@lists.infradead.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v4 1/2] sh: mm: make use of new memblocks_present() helper
Date: Wed, 23 Jan 2019 11:56:01 -0800 (PST) [thread overview]
Message-ID: <mhng-96f28491-e123-459a-b09c-88732de06bbf@palmer-si-x1c4> (raw)
On Tue, 15 Jan 2019 09:30:44 PST (-0800), logang@deltatee.com wrote:
>
>
> On 2019-01-15 6:58 a.m., Christoph Hellwig wrote:
>> Reviewed-by: Christoph Hellwig <hch@lst.de>
>>
>> Probably no need to keep this in a series with the RISC-V code, this can
>> be queued up by the sh folks independently.
>
> Oh, yeah, sorry, I obviously didn't pay enough attention to this when I
> resent it. I sent the similar Arm changes to the appropriate list and,
> yes, the sh ones should go to that maintainer.
>
> @Palmer: if you can just look at taking the second patch, I'll resubmit
> the first one to the appropriate list.
Works for me. I'll queue the second patch into my staging branch, targeted for
the next merge window.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2019-01-23 22:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 19:56 Palmer Dabbelt [this message]
2019-01-23 20:31 ` [PATCH v4 1/2] sh: mm: make use of new memblocks_present() helper Logan Gunthorpe
2019-03-19 17:56 ` Logan Gunthorpe
2019-03-20 2:54 ` Palmer Dabbelt
2019-03-20 17:43 ` Logan Gunthorpe
2019-03-21 8:37 ` Palmer Dabbelt
-- strict thread matches above, loose matches on Subject: below --
2019-01-09 20:39 [PATCH v4 0/2] [PATCH v2 0/6] sparsemem support for RISC-V Logan Gunthorpe
2019-01-09 20:39 ` [PATCH v4 1/2] sh: mm: make use of new memblocks_present() helper Logan Gunthorpe
2019-01-15 13:58 ` Christoph Hellwig
2019-01-15 17:30 ` Logan Gunthorpe
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-96f28491-e123-459a-b09c-88732de06bbf@palmer-si-x1c4 \
--to=palmer@sifive.com \
--cc=dalias@libc.org \
--cc=dan.j.williams@intel.com \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=logang@deltatee.com \
--cc=robh@kernel.org \
--cc=sbates@raithlin.com \
--cc=ysato@users.sourceforge.jp \
/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).