From: Dan Williams <dan.j.williams@intel.com>
To: Drew Fustini <drew@pdp7.com>,
Dan Williams <dan.j.williams@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Dave Jiang <dave.jiang@intel.com>, <nvdimm@lists.linux.dev>,
<ira.weiny@intel.com>
Cc: Oliver O'Halloran <oohall@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Drew Fustini <drew@pdp7.com>,
Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH v3] dt-bindings: pmem: Convert binding to YAML
Date: Fri, 6 Jun 2025 19:29:41 -0700 [thread overview]
Message-ID: <6843a4159242e_249110032@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <20250606184405.359812-4-drew@pdp7.com>
[ add Ira ]
Drew Fustini wrote:
> Convert the PMEM device tree binding from text to YAML. This will allow
> device trees with pmem-region nodes to pass dtbs_check.
>
> Acked-by: Conor Dooley <conor.dooley@microchip.com>
> Acked-by: Oliver O'Halloran <oohall@gmail.com>
> Signed-off-by: Drew Fustini <drew@pdp7.com>
> ---
> Dan/Dave/Vishal: does it make sense for this pmem binding patch to go
> through the nvdimm tree?
Ira has been handling nvdimm pull requests as of late. Oliver's ack is
sufficient for me.
Acked-by: Dan Williams <dan.j.williams@intel.com>
@Ira do you have anything else pending?
next prev parent reply other threads:[~2025-06-07 2:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 18:11 [PATCH v3] dt-bindings: pmem: Convert binding to YAML Drew Fustini
2025-06-07 2:29 ` Dan Williams [this message]
2025-06-09 14:31 ` Ira Weiny
2025-06-10 2:10 ` Drew Fustini
2025-06-10 18:43 ` Drew Fustini
2025-06-10 22:05 ` Ira Weiny
2025-06-09 13:32 ` Rob Herring
2025-06-10 18:14 ` Drew Fustini
2025-06-11 14:33 ` Ira Weiny
2025-06-11 17:11 ` Drew Fustini
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=6843a4159242e_249110032@dwillia2-xfh.jf.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=dave.jiang@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=drew@pdp7.com \
--cc=ira.weiny@intel.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=oohall@gmail.com \
--cc=robh@kernel.org \
--cc=vishal.l.verma@intel.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