From: Christoph Hellwig <hch@infradead.org>
To: Logan Gunthorpe <logang@deltatee.com>
Cc: linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
Rob Herring <robh@kernel.org>, Rich Felker <dalias@libc.org>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Palmer Dabbelt <palmer@sifive.com>,
Stephen Bates <sbates@raithlin.com>,
Dan Williams <dan.j.williams@intel.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v4 1/2] sh: mm: make use of new memblocks_present() helper
Date: Tue, 15 Jan 2019 05:58:19 -0800 [thread overview]
Message-ID: <20190115135819.GK28946@infradead.org> (raw)
In-Reply-To: <20190109203911.7887-2-logang@deltatee.com>
On Wed, Jan 09, 2019 at 01:39:10PM -0700, Logan Gunthorpe wrote:
> Cleanup the open coded for_each_memblock() loop that is equivalent
> to the new memblocks_present() helper.
Looks good:
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.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Logan Gunthorpe <logang@deltatee.com>
Cc: Rob Herring <robh@kernel.org>, Rich Felker <dalias@libc.org>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Palmer Dabbelt <palmer@sifive.com>,
linux-kernel@vger.kernel.org, Stephen Bates <sbates@raithlin.com>,
linux-riscv@lists.infradead.org, Christoph Hellwig <hch@lst.de>,
Dan Williams <dan.j.williams@intel.com>
Subject: Re: [PATCH v4 1/2] sh: mm: make use of new memblocks_present() helper
Date: Tue, 15 Jan 2019 05:58:19 -0800 [thread overview]
Message-ID: <20190115135819.GK28946@infradead.org> (raw)
In-Reply-To: <20190109203911.7887-2-logang@deltatee.com>
On Wed, Jan 09, 2019 at 01:39:10PM -0700, Logan Gunthorpe wrote:
> Cleanup the open coded for_each_memblock() loop that is equivalent
> to the new memblocks_present() helper.
Looks good:
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.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2019-01-15 13:58 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
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 ` Logan Gunthorpe
2019-01-09 20:39 ` [PATCH v4 1/2] sh: mm: make use of new memblocks_present() helper Logan Gunthorpe
2019-01-09 20:39 ` Logan Gunthorpe
2019-01-15 13:58 ` Christoph Hellwig [this message]
2019-01-15 13:58 ` Christoph Hellwig
2019-01-15 17:30 ` Logan Gunthorpe
2019-01-15 17:30 ` Logan Gunthorpe
2019-01-09 20:39 ` [PATCH v4 2/2] RISC-V: Implement sparsemem Logan Gunthorpe
2019-01-09 20:39 ` Logan Gunthorpe
2019-01-15 13:58 ` Christoph Hellwig
2019-01-15 13:58 ` Christoph Hellwig
2019-07-31 6:30 ` Greentime Hu
2019-07-31 6:30 ` Greentime Hu
2019-07-31 17:07 ` Logan Gunthorpe
2019-07-31 17:07 ` Logan Gunthorpe
2019-08-01 3:34 ` Greentime Hu
2019-08-01 3:34 ` Greentime Hu
[not found] ` <CAEbi=3eZcgWevpX9VO9ohgxVDFVprk_t52Xbs3-TdtZ+js3NVA@mail.gmail.com>
2019-08-09 15:46 ` Logan Gunthorpe
2019-08-09 15:46 ` Logan Gunthorpe
2019-08-09 17:01 ` Greentime Hu
2019-08-09 17:01 ` Greentime Hu
2019-08-09 19:03 ` Logan Gunthorpe
2019-08-09 19:03 ` Logan Gunthorpe
2019-08-12 4:01 ` Greentime Hu
2019-08-12 4:01 ` Greentime Hu
2019-08-12 15:51 ` Logan Gunthorpe
2019-08-12 15:51 ` Logan Gunthorpe
2019-08-13 6:04 ` Greentime Hu
2019-08-13 6:04 ` Greentime Hu
2019-08-13 16:14 ` Logan Gunthorpe
2019-08-13 16:14 ` Logan Gunthorpe
2019-08-13 16:39 ` Paul Walmsley
2019-08-13 16:39 ` Paul Walmsley
2019-08-13 16:48 ` Paul Walmsley
2019-08-13 16:48 ` Paul Walmsley
2019-08-13 16:48 ` Paul Walmsley
2019-08-13 16:49 ` Logan Gunthorpe
2019-08-13 16:49 ` Logan Gunthorpe
2019-08-14 13:35 ` Greentime Hu
2019-08-14 13:35 ` Greentime Hu
2019-08-14 16:56 ` Logan Gunthorpe
2019-08-14 16:56 ` Logan Gunthorpe
2019-08-14 17:40 ` Paul Walmsley
2019-08-14 17:40 ` Paul Walmsley
2019-08-14 17:46 ` Logan Gunthorpe
2019-08-14 17:46 ` Logan Gunthorpe
2019-08-14 20:09 ` Paul Walmsley
2019-08-14 20:09 ` Paul Walmsley
2019-08-14 22:21 ` Logan Gunthorpe
2019-08-14 22:21 ` Logan Gunthorpe
2019-08-15 9:31 ` Greentime Hu
2019-08-15 9:31 ` Greentime Hu
2019-08-15 16:20 ` Logan Gunthorpe
2019-08-15 16:20 ` Logan Gunthorpe
2019-08-16 2:07 ` Greentime Hu
2019-08-16 2:07 ` Greentime Hu
2019-01-23 19:56 [PATCH v4 1/2] sh: mm: make use of new memblocks_present() helper Palmer Dabbelt
2019-01-23 19:56 ` Palmer Dabbelt
2019-01-23 20:31 ` Logan Gunthorpe
2019-01-23 20:31 ` Logan Gunthorpe
2019-03-19 17:56 ` Logan Gunthorpe
2019-03-19 17:56 ` Logan Gunthorpe
2019-03-20 2:54 ` Palmer Dabbelt
2019-03-20 2:54 ` Palmer Dabbelt
2019-03-20 17:43 ` Logan Gunthorpe
2019-03-20 17:43 ` Logan Gunthorpe
2019-03-21 8:37 ` Palmer Dabbelt
2019-03-21 8:37 ` 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=20190115135819.GK28946@infradead.org \
--to=hch@infradead.org \
--cc=dalias@libc.org \
--cc=dan.j.williams@intel.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=logang@deltatee.com \
--cc=palmer@sifive.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.