From: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Oliver O'Halloran <oohall-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org
Subject: Re: [PATCH 2/3] libnvdimm: Add a device-tree interface
Date: Thu, 16 Nov 2017 08:29:26 -0600 [thread overview]
Message-ID: <20171116142926.cdvx2st72tnu7gi7@rob-hp-laptop> (raw)
In-Reply-To: <20171115175131.23631-2-oohall-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On Thu, Nov 16, 2017 at 04:51:30AM +1100, Oliver O'Halloran wrote:
> A fairly bare-bones set of device-tree bindings so libnvdimm can be used
> on powerpc and other device-tree based platforms.
>
> Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> Signed-off-by: Oliver O'Halloran <oohall-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> ---
> .../devicetree/bindings/nvdimm/nvdimm-bus.txt | 69 +++++++
Also, please split bindings to a separate patch.
> MAINTAINERS | 8 +
> drivers/nvdimm/Kconfig | 10 +
> drivers/nvdimm/Makefile | 1 +
> drivers/nvdimm/of_nvdimm.c | 202 +++++++++++++++++++++
> 5 files changed, 290 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/nvdimm/nvdimm-bus.txt
> create mode 100644 drivers/nvdimm/of_nvdimm.c
prev parent reply other threads:[~2017-11-16 14:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171115175131.23631-1-oohall@gmail.com>
[not found] ` <20171115175131.23631-1-oohall-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-11-15 17:51 ` [PATCH 2/3] libnvdimm: Add a device-tree interface Oliver O'Halloran
[not found] ` <20171115175131.23631-2-oohall-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-11-16 14:28 ` Rob Herring
2017-11-24 6:36 ` Michael Ellerman
2017-11-16 14:29 ` Rob Herring [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=20171116142926.cdvx2st72tnu7gi7@rob-hp-laptop \
--to=robh-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org \
--cc=linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=oohall-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/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