From: Gabriel Fernandez <gabriel.fernandez@st.com>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Russell King <linux@armlinux.org.uk>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@st.com>,
Michael Turquette <mturquette@baylibre.com>,
Nicolas Pitre <nico@linaro.org>, Arnd Bergmann <arnd@arndb.de>,
<daniel.thompson@linaro.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-clk@vger.kernel.org>,
<ludovic.barre@st.com>, <olivier.bideau@st.com>,
<amelie.delaunay@st.com>
Subject: Re: [PATCH v2 0/6] STM32F4 Add RTC & QSPI clocks
Date: Wed, 19 Oct 2016 10:34:38 +0200 [thread overview]
Message-ID: <d878b846-556d-180b-8ebf-2d06646efb58@st.com> (raw)
In-Reply-To: <20161018235108.GP8871@codeaurora.org>
Hi Stephen,
On 10/19/2016 01:51 AM, Stephen Boyd wrote:
> On 10/14, gabriel.fernandez@st.com wrote:
>> Gabriel Fernandez (6):
>> clk: stm32f4: Add LSI & LSE clocks
>> ARM: dts: stm32f429: add LSI and LSE clocks
>> arm: stmf32: Enable SYSCON
>> clk: stm32f4: Add RTC clock
>> clk: stm32f469: Add QSPI clock
>> ARM: dts: stm32f429: Add QSPI clock
> Can the clk patches be picked without causing problems for
> existing dt changes? Do you want an ack from clk maintainers
> instead of us picking the clk patches up? The series has
> intermingled clk and dts changes so I'm confused.
>
Thanks for reviewing.
Normally DT patches will be taken by STM32 maintainer, but yes there is
a dependency between patch 1 & 2, so if you push the patch 1 into
clk-next tree you have to take also patch 2.
You have to be synchronized with Alexandre Torgue.
Best Regards
Gabriel
next prev parent reply other threads:[~2016-10-19 14:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-14 9:18 gabriel.fernandez
2016-10-14 9:18 ` [PATCH v2 1/6] clk: stm32f4: Add LSI & LSE clocks gabriel.fernandez
2016-10-19 20:24 ` Stephen Boyd
2016-10-20 7:47 ` Gabriel Fernandez
2016-10-20 16:05 ` Gabriel Fernandez
2016-10-14 9:18 ` [PATCH v2 2/6] ARM: dts: stm32f429: add LSI and " gabriel.fernandez
2016-10-14 9:18 ` [PATCH v2 3/6] arm: stmf32: Enable SYSCON gabriel.fernandez
2016-10-14 9:18 ` [PATCH v2 4/6] clk: stm32f4: Add RTC clock gabriel.fernandez
2016-10-19 20:45 ` Stephen Boyd
2016-10-20 7:50 ` Gabriel Fernandez
2016-10-20 7:55 ` Gabriel Fernandez
2016-10-14 9:18 ` [PATCH v2 5/6] clk: stm32f469: Add QSPI clock gabriel.fernandez
2016-10-18 14:17 ` Rob Herring
2016-10-19 20:32 ` Stephen Boyd
2016-10-20 15:44 ` Gabriel Fernandez
2016-10-14 9:18 ` [PATCH v2 6/6] ARM: dts: stm32f429: " gabriel.fernandez
2016-11-03 16:45 ` Alexandre Torgue
2016-10-18 23:51 ` [PATCH v2 0/6] STM32F4 Add RTC & QSPI clocks Stephen Boyd
2016-10-19 8:34 ` Gabriel Fernandez [this message]
2016-10-19 20:29 ` Stephen Boyd
2016-10-20 7:52 ` Gabriel Fernandez
2016-11-03 8:52 ` Alexandre Torgue
2016-11-03 8:57 ` Gabriel Fernandez
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=d878b846-556d-180b-8ebf-2d06646efb58@st.com \
--to=gabriel.fernandez@st.com \
--cc=alexandre.torgue@st.com \
--cc=amelie.delaunay@st.com \
--cc=arnd@arndb.de \
--cc=daniel.thompson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=ludovic.barre@st.com \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=mturquette@baylibre.com \
--cc=nico@linaro.org \
--cc=olivier.bideau@st.com \
--cc=robh+dt@kernel.org \
--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
all inboxes | Powered by JetHome®