All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@xilinx.com>
To: Stephen Boyd <sboyd@kernel.org>,
	Rajan Vaja <rajan.vaja@xilinx.com>, <michal.simek@xilinx.com>,
	<mturquette@baylibre.com>, <olof@lixom.net>,
	<shubhrajyoti.datta@xilinx.com>
Cc: <jolly.shah@xilinx.com>, <linux-clk@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] clk: zynqmp: handle fixed factor param query error
Date: Mon, 5 Nov 2018 08:38:35 +0100	[thread overview]
Message-ID: <26e50d25-a02b-5ece-d12d-8c6ee208a845@xilinx.com> (raw)
In-Reply-To: <153978972088.5275.4505414322881956934@swboyd.mtv.corp.google.com>

On 17. 10. 18 17:22, Stephen Boyd wrote:
> Quoting Rajan Vaja (2018-10-17 00:46:32)
>> Return proper error code in case query for fixed factor
>> parameter fails. This also fixes build warning for set
>> but not used variable 'ret'.
>>
>> Signed-off-by: Rajan Vaja <rajan.vaja@xilinx.com>
> 
> Fixes tag? And I think this is going through arm-soc already? If so,
> 
> Acked-by: Stephen Boyd <sboyd@kernel.org>
> 
> with the appropriate fixes tag added.

It was really just about to merge this via arm-soc tree because of
dependency on firmware itself.
It is the part of v4.20-rc1 now and it can go via your tree.

Anyway v2 is required with Fixed tag anyway.
Rajan: Please send it v2 with Acked above.

Thanks,
Michal

WARNING: multiple messages have this Message-ID (diff)
From: michal.simek@xilinx.com (Michal Simek)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: zynqmp: handle fixed factor param query error
Date: Mon, 5 Nov 2018 08:38:35 +0100	[thread overview]
Message-ID: <26e50d25-a02b-5ece-d12d-8c6ee208a845@xilinx.com> (raw)
In-Reply-To: <153978972088.5275.4505414322881956934@swboyd.mtv.corp.google.com>

On 17. 10. 18 17:22, Stephen Boyd wrote:
> Quoting Rajan Vaja (2018-10-17 00:46:32)
>> Return proper error code in case query for fixed factor
>> parameter fails. This also fixes build warning for set
>> but not used variable 'ret'.
>>
>> Signed-off-by: Rajan Vaja <rajan.vaja@xilinx.com>
> 
> Fixes tag? And I think this is going through arm-soc already? If so,
> 
> Acked-by: Stephen Boyd <sboyd@kernel.org>
> 
> with the appropriate fixes tag added.

It was really just about to merge this via arm-soc tree because of
dependency on firmware itself.
It is the part of v4.20-rc1 now and it can go via your tree.

Anyway v2 is required with Fixed tag anyway.
Rajan: Please send it v2 with Acked above.

Thanks,
Michal

  reply	other threads:[~2018-11-05  7:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-17  7:46 [PATCH] clk: zynqmp: handle fixed factor param query error Rajan Vaja
2018-10-17  7:46 ` Rajan Vaja
2018-10-17 15:22 ` Stephen Boyd
2018-10-17 15:22   ` Stephen Boyd
2018-11-05  7:38   ` Michal Simek [this message]
2018-11-05  7:38     ` Michal Simek
2018-11-14  7:47     ` Rajan Vaja
2018-11-14  7:47       ` Rajan Vaja
2018-11-14  7:46 ` [PATCH v2] " Rajan Vaja
2018-11-14  7:46   ` Rajan Vaja
2018-11-14 22:30   ` Stephen Boyd
2018-11-14 22:30     ` Stephen Boyd

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=26e50d25-a02b-5ece-d12d-8c6ee208a845@xilinx.com \
    --to=michal.simek@xilinx.com \
    --cc=jolly.shah@xilinx.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=olof@lixom.net \
    --cc=rajan.vaja@xilinx.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.