From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Michal Simek <michal.simek@amd.com>
Cc: Shubhrajyoti Datta <shubhrajyoti.datta@xilinx.com>,
linux-clk@vger.kernel.org, git <git@xilinx.com>,
Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Arnd Bergmann <arnd@arndb.de>,
robh+dt@kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v14 0/5] clk: clocking-wizard: Driver updates
Date: Thu, 14 Jul 2022 13:35:04 +0200 [thread overview]
Message-ID: <Ys//aPLkLGaooYYw@kroah.com> (raw)
In-Reply-To: <155c77c3-25d9-7edc-35bd-56e6cfb19ac6@amd.com>
On Thu, Jul 14, 2022 at 01:26:58PM +0200, Michal Simek wrote:
> Hi Stephen and Michael,
>
> On 4/11/22 12:04, Shubhrajyoti Datta wrote:
> > The patch does the following
> > Update the versions of the clocking wizard ip.
> > Move from staging to clk directory.
> > Update the bindings.
> >
> > v12:
> > No change.
> > Rebased
> > v13:
> > Update the clocking compatible
> > Add the change removing the driver from staging
> > v14:
> > Moved to the xilinx folder
> >
> > Shubhrajyoti Datta (5):
> > dt-bindings: add documentation of xilinx clocking wizard
> > clk: clocking-wizard: Add the clockwizard to clk directory
> > clk: clocking-wizard: Rename nr-outputs to xlnx,nr-outputs
> > clk: clocking-wizard: Fix the reconfig for 5.2
> > clk: clocking-wizard: Update the compatible
> >
> > .../bindings/clock/xlnx,clocking-wizard.yaml | 77 +++++++++++++++++++
> > drivers/clk/xilinx/Kconfig | 11 +++
> > drivers/clk/xilinx/Makefile | 1 +
> > .../xilinx}/clk-xlnx-clock-wizard.c | 19 +++--
> > drivers/staging/Kconfig | 2 -
> > drivers/staging/Makefile | 1 -
> > drivers/staging/clocking-wizard/Kconfig | 10 ---
> > drivers/staging/clocking-wizard/Makefile | 2 -
> > drivers/staging/clocking-wizard/TODO | 13 ----
> > .../staging/clocking-wizard/dt-binding.txt | 30 --------
> > 10 files changed, 103 insertions(+), 63 deletions(-)
> > create mode 100644 Documentation/devicetree/bindings/clock/xlnx,clocking-wizard.yaml
> > rename drivers/{staging/clocking-wizard => clk/xilinx}/clk-xlnx-clock-wizard.c (96%)
> > delete mode 100644 drivers/staging/clocking-wizard/Kconfig
> > delete mode 100644 drivers/staging/clocking-wizard/Makefile
> > delete mode 100644 drivers/staging/clocking-wizard/TODO
> > delete mode 100644 drivers/staging/clocking-wizard/dt-binding.txt
> >
>
> I was looking at comment in v13 and moving to xilinx folder was done in v14.
> v13: https://lore.kernel.org/r/cover.1631623906.git.shubhrajyoti.datta@xilinx.com
>
> dt binding is also reviewed by Rob already.
>
> You asked there to get confirmation from Greg that it can be moved out of
> staging. I didn't see any reply from Greg about it but not sure if this is
> really required to get.
> Greg: Can you please ACK it or comment?
No objection from me if others want to maintainer it in their portion of
the kernel tree:
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
prev parent reply other threads:[~2022-07-14 11:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 10:04 [PATCH v14 0/5] clk: clocking-wizard: Driver updates Shubhrajyoti Datta
2022-04-11 10:04 ` [PATCH v14 1/5] dt-bindings: add documentation of xilinx clocking wizard Shubhrajyoti Datta
2022-04-14 1:02 ` Rob Herring
2022-08-23 2:02 ` Stephen Boyd
2022-04-11 10:04 ` [PATCH v14 2/5] clk: clocking-wizard: Move clocking-wizard out Shubhrajyoti Datta
2022-08-23 2:03 ` Stephen Boyd
2022-04-11 10:04 ` [PATCH v14 3/5] clk: clocking-wizard: Rename nr-outputs to xlnx,nr-outputs Shubhrajyoti Datta
2022-08-23 2:03 ` Stephen Boyd
2022-04-11 10:04 ` [PATCH v14 4/5] clk: clocking-wizard: Fix the reconfig for 5.2 Shubhrajyoti Datta
2022-08-23 2:03 ` Stephen Boyd
2022-04-11 10:04 ` [PATCH v14 5/5] clk: clocking-wizard: Update the compatible Shubhrajyoti Datta
2022-08-23 2:04 ` Stephen Boyd
2022-06-13 5:23 ` [PATCH v14 0/5] clk: clocking-wizard: Driver updates Shubhrajyoti Datta
2022-07-14 11:26 ` Michal Simek
2022-07-14 11:35 ` Greg Kroah-Hartman [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=Ys//aPLkLGaooYYw@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=git@xilinx.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=shubhrajyoti.datta@xilinx.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;
as well as URLs for NNTP newsgroup(s).