linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: kw@linux.com, Michal Simek <michal.simek@xilinx.com>,
	git@xilinx.com, bharat.kumar.gogada@xilinx.com, monstr@monstr.eu,
	linux-kernel@vger.kernel.org
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	linux-arm-kernel@lists.infradead.org,
	Rob Herring <robh@kernel.org>,
	linux-pci@vger.kernel.org,
	Ravi Kiran Gummaluri <rgummal@xilinx.com>,
	Marc Zyngier <maz@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	Bjorn Helgaas <bhelgaas@google.com>,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v3 0/2] PCI: xilinx-nwl: Add clock handling
Date: Fri, 13 Aug 2021 15:40:28 +0100	[thread overview]
Message-ID: <162886561478.21160.11916586885494837733.b4-ty@arm.com> (raw)
In-Reply-To: <cover.1624618100.git.michal.simek@xilinx.com>

On Fri, 25 Jun 2021 12:48:21 +0200, Michal Simek wrote:
> this small series add support for enabling PCIe reference clock by driver.
> 
> Thanks,
> Michal
> 
> Changes in v3:
> - use PCIe instead of pcie
> - add stable cc
> - update commit message - reported by Krzysztof
> 
> [...]

Applied to pci/xilinx-nwl, thanks!

[1/2] dt-bindings: pci: xilinx-nwl: Document optional clock property
      https://git.kernel.org/lpieralisi/pci/c/4d79e36718
[2/2] PCI: xilinx-nwl: Enable the clock through CCF
      https://git.kernel.org/lpieralisi/pci/c/de0a01f529

Thanks,
Lorenzo

      parent reply	other threads:[~2021-08-13 14:40 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
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 [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=162886561478.21160.11916586885494837733.b4-ty@arm.com \
    --to=lorenzo.pieralisi@arm.com \
    --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=maz@kernel.org \
    --cc=michal.simek@xilinx.com \
    --cc=monstr@monstr.eu \
    --cc=rgummal@xilinx.com \
    --cc=robh+dt@kernel.org \
    --cc=robh@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).