From: Olof Johansson <olof@lixom.net>
To: Jolly Shah <JOLLYS@xilinx.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
Michal Simek <michals@xilinx.com>,
ARM-SoC Maintainers <arm@kernel.org>,
linux-clk <linux-clk@vger.kernel.org>,
Rajan Vaja <RAJANV@xilinx.com>,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 2/4] firmware: xilinx: Add zynqmp IOCTL API for device control
Date: Fri, 28 Sep 2018 14:12:48 -0700 [thread overview]
Message-ID: <CAOesGMiUnVrnW1VDh1CKRKGpkwAC9G8tiHjpb+7bss6LpPWU-A@mail.gmail.com> (raw)
In-Reply-To: <BL2PR02MB21308D0B6AF76A8094E70863B8EC0@BL2PR02MB2130.namprd02.prod.outlook.com>
On Fri, Sep 28, 2018 at 10:15 AM Jolly Shah <JOLLYS@xilinx.com> wrote:
>
> Hi Olof,
>
> Thanks for the review. Pushed v4 with suggested fixes. Let us know if series looks good and we can create pull request for same.
>
> Thanks,
> Jolly Shah
I'm happy with this one, thanks for revising the patchset with the fixes.
Feel free to add:
Acked-by: Olof Johansson <olof@lixom.net>
to the patches.
-Olof
next prev parent reply other threads:[~2018-09-28 21:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-26 18:12 [PATCH v3 0/4] drivers: clk: Add ZynqMP clock driver support Jolly Shah
2018-09-26 18:12 ` [PATCH v3 1/4] Documentation: xilinx: Add documentation for eemi APIs Jolly Shah
2018-09-26 18:12 ` [PATCH v3 2/4] firmware: xilinx: Add zynqmp IOCTL API for device control Jolly Shah
2018-09-26 20:48 ` Olof Johansson
2018-09-28 17:15 ` Jolly Shah
2018-09-28 21:12 ` Olof Johansson [this message]
2018-10-01 13:17 ` Michal Simek
2018-10-01 17:26 ` Olof Johansson
2018-10-02 10:53 ` Michal Simek
2018-09-26 18:13 ` [PATCH v3 3/4] dt-bindings: clock: Add bindings for ZynqMP clock driver Jolly Shah
2018-09-26 18:13 ` [PATCH v3 4/4] drivers: clk: Add " Jolly Shah
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=CAOesGMiUnVrnW1VDh1CKRKGpkwAC9G8tiHjpb+7bss6LpPWU-A@mail.gmail.com \
--to=olof@lixom.net \
--cc=JOLLYS@xilinx.com \
--cc=RAJANV@xilinx.com \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michals@xilinx.com \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.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).