linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@xilinx.com>
To: Olof Johansson <olof@lixom.net>, Michal Simek <michal.simek@xilinx.com>
Cc: Jolly Shah <JOLLYS@xilinx.com>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@codeaurora.org>,
	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: Tue, 2 Oct 2018 12:53:25 +0200	[thread overview]
Message-ID: <3b9ddd6a-7965-af51-cae5-4135f34de6c4@xilinx.com> (raw)
In-Reply-To: <CAOesGMixcQS605kmpW+n-yWBGWu4Dz5SXH396mrWCUfQjfcWcQ@mail.gmail.com>

On 1.10.2018 19:26, Olof Johansson wrote:
> On Mon, Oct 1, 2018 at 6:17 AM Michal Simek <michal.simek@xilinx.com> wrote:
>>
>> Hi,
>>
>> On 28.9.2018 23:12, Olof Johansson wrote:
>>> 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.
>>
>> Just for clarification. I have checked driver/clk and patches should
>> still go via Michael or Stephen.
>> Firmware code is already in arm-soc tree that's why I would expect
>> Michael/Stephen should review it and then it shouldn't be a problem to
>> take this via arm-soc tree.
>>
>> Olof: Please correct me if I am wrong and you are happy to take it via
>> arm-soc directly.
> 
> Honestly it might be easiest for you to prepare one branch and send to
> all parties in case you have contents you expect to go on top, but
> besides that I'd be fine with merging through either tree.

ok.

Stephen: Can you please take a look at 4/4?
dt binding was already reviewed that's when we have ACK from 4/4 I will
prepare that branch.

Thanks,
Michal

  reply	other threads:[~2018-10-02 10:54 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
2018-10-01 13:17         ` Michal Simek
2018-10-01 17:26           ` Olof Johansson
2018-10-02 10:53             ` Michal Simek [this message]
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=3b9ddd6a-7965-af51-cae5-4135f34de6c4@xilinx.com \
    --to=michal.simek@xilinx.com \
    --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=mturquette@baylibre.com \
    --cc=olof@lixom.net \
    --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).