From: Rob Herring <robh@kernel.org>
To: Michal Simek <michal.simek@xilinx.com>
Cc: git@xilinx.com, monstr@monstr.eu, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Bjorn Helgaas <bhelgaas@google.com>,
devicetree@vger.kernel.org, linux-pci@vger.kernel.org,
kw@linux.com, bharat.kumar.gogada@xilinx.com,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v3 1/2] dt-bindings: pci: xilinx-nwl: Document optional clock property
Date: Wed, 14 Jul 2021 13:47:08 -0600 [thread overview]
Message-ID: <20210714194708.GA3236304@robh.at.kernel.org> (raw)
In-Reply-To: <67aa2c189337181bb2d7721fb616db5640587d2a.1624618100.git.michal.simek@xilinx.com>
On Fri, 25 Jun 2021 12:48:22 +0200, Michal Simek wrote:
> Clock property hasn't been documented in binding document but it is used
> for quite a long time where clock was specified by commit 9c8a47b484ed
> ("arm64: dts: xilinx: Add the clock nodes for zynqmp").
>
> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
> ---
>
> (no changes since v2)
>
> Changes in v2:
> - new patch in this series because I found that it has never been sent
>
> Bharat: Can you please start to work on converting it to yaml?
>
> ---
> Documentation/devicetree/bindings/pci/xilinx-nwl-pcie.txt | 1 +
> 1 file changed, 1 insertion(+)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-07-14 19:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-25 10:48 [PATCH v3 0/2] PCI: xilinx-nwl: Add clock handling Michal Simek
2021-06-25 10:48 ` [PATCH v3 1/2] dt-bindings: pci: xilinx-nwl: Document optional clock property Michal Simek
2021-07-14 19:47 ` Rob Herring [this message]
2021-06-25 10:48 ` [PATCH v3 2/2] PCI: xilinx-nwl: Enable the clock through CCF Michal Simek
2021-08-06 10:28 ` [PATCH v3 0/2] PCI: xilinx-nwl: Add clock handling Michal Simek
2021-08-13 14:40 ` Lorenzo Pieralisi
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=20210714194708.GA3236304@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=bharat.kumar.gogada@xilinx.com \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=git@xilinx.com \
--cc=kw@linux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).