Linux clock framework development
 help / color / mirror / Atom feed
From: Gabriel Fernandez <gabriel.fernandez@st.com>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	Alexandre Torgue <alexandre.torgue@st.com>,
	Nicolas Pitre <nico@linaro.org>, Arnd Bergmann <arnd@arndb.de>,
	<daniel.thompson@linaro.org>, <andrea.merello@gmail.com>,
	<radoslaw.pietrzyk@gmail.com>, <linux-clk@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] STM32F4 clock fixes
Date: Thu, 16 Mar 2017 09:04:40 +0100	[thread overview]
Message-ID: <d400ff60-06ce-c765-981a-2dce4b1de89d@st.com> (raw)
In-Reply-To: <20170315204307.GK10239@codeaurora.org>

Hi Stephen,

On 03/15/2017 09:43 PM, Stephen Boyd wrote:
> On 03/15, gabriel.fernandez@st.com wrote:
>> From: Gabriel Fernandez <gabriel.fernandez@st.com>
>>
>> This patch-set contains 2 fixes.
>> One concerning exclusion of wrong values for PLLQ (0 & 1)
>> And the second is a fix about timeout management of PLL and LSE/LSI clocks.
> But neither of the patches have a "Fixes" tag. Can you please
> indicate what commits they're fixing?
>
Okay i will send a v2 with "Fixes" tags

BR

Gabriel

      reply	other threads:[~2017-03-16  8:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-15 14:27 [PATCH 0/2] STM32F4 clock fixes gabriel.fernandez
2017-03-15 14:27 ` [PATCH 1/2] clk: stm32f4: fix: exclude values 0 and 1 for PLLQ gabriel.fernandez
2017-03-15 14:27 ` [PATCH 2/2] clk: stm32f4: fix timeout management for pll and ready gate gabriel.fernandez
2017-03-15 20:43 ` [PATCH 0/2] STM32F4 clock fixes Stephen Boyd
2017-03-16  8:04   ` Gabriel Fernandez [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=d400ff60-06ce-c765-981a-2dce4b1de89d@st.com \
    --to=gabriel.fernandez@st.com \
    --cc=alexandre.torgue@st.com \
    --cc=andrea.merello@gmail.com \
    --cc=arnd@arndb.de \
    --cc=daniel.thompson@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=mturquette@baylibre.com \
    --cc=nico@linaro.org \
    --cc=radoslaw.pietrzyk@gmail.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