From: Lee Jones <lee.jones@linaro.org>
To: Mark Brown <broonie@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel@stlinux.com,
maxime.coquelin@st.com, patrice.chotard@st.com,
mturquette@baylibre.com, sboyd@codeaurora.org,
linux-clk@vger.kernel.org, linux-spi@vger.kernel.org
Subject: Re: [PATCH 6/6] spi: st-ssc4: Remove 'no clocking' hack
Date: Thu, 30 Jun 2016 21:52:15 +0100 [thread overview]
Message-ID: <20160630205215.GF1707@dell> (raw)
In-Reply-To: <20160607151712.GA7510@sirena.org.uk>
On Tue, 07 Jun 2016, Mark Brown wrote:
> On Tue, Jun 07, 2016 at 12:19:30PM +0100, Lee Jones wrote:
> > Due to the newly upstreamed 'critical clocks' API we can now
> > safely handle clocking in the SPI and I2C drivers without fear
> > of catastrophically crippling the running platform.
>
> Acked-by: Mark Brown <broonie@kernel.org>
We really need to guarantee that this goes in *after* the other
patches have landed, and it looks like they're heading in via their
own respective trees. Any chance you can hold this back and submit it
via your v4.8-fixes submission?
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
WARNING: multiple messages have this Message-ID (diff)
From: Lee Jones <lee.jones@linaro.org>
To: Mark Brown <broonie@kernel.org>
Cc: kernel@stlinux.com, mturquette@baylibre.com,
sboyd@codeaurora.org, patrice.chotard@st.com,
linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
maxime.coquelin@st.com
Subject: Re: [PATCH 6/6] spi: st-ssc4: Remove 'no clocking' hack
Date: Thu, 30 Jun 2016 21:52:15 +0100 [thread overview]
Message-ID: <20160630205215.GF1707@dell> (raw)
In-Reply-To: <20160607151712.GA7510@sirena.org.uk>
On Tue, 07 Jun 2016, Mark Brown wrote:
> On Tue, Jun 07, 2016 at 12:19:30PM +0100, Lee Jones wrote:
> > Due to the newly upstreamed 'critical clocks' API we can now
> > safely handle clocking in the SPI and I2C drivers without fear
> > of catastrophically crippling the running platform.
>
> Acked-by: Mark Brown <broonie@kernel.org>
We really need to guarantee that this goes in *after* the other
patches have landed, and it looks like they're heading in via their
own respective trees. Any chance you can hold this back and submit it
via your v4.8-fixes submission?
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 6/6] spi: st-ssc4: Remove 'no clocking' hack
Date: Thu, 30 Jun 2016 21:52:15 +0100 [thread overview]
Message-ID: <20160630205215.GF1707@dell> (raw)
In-Reply-To: <20160607151712.GA7510@sirena.org.uk>
On Tue, 07 Jun 2016, Mark Brown wrote:
> On Tue, Jun 07, 2016 at 12:19:30PM +0100, Lee Jones wrote:
> > Due to the newly upstreamed 'critical clocks' API we can now
> > safely handle clocking in the SPI and I2C drivers without fear
> > of catastrophically crippling the running platform.
>
> Acked-by: Mark Brown <broonie@kernel.org>
We really need to guarantee that this goes in *after* the other
patches have landed, and it looks like they're heading in via their
own respective trees. Any chance you can hold this back and submit it
via your v4.8-fixes submission?
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2016-06-30 20:57 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 11:19 [PATCH 0/6] clk: sti: Add support for critical clocks Lee Jones
2016-06-07 11:19 ` Lee Jones
2016-06-07 11:19 ` [PATCH 1/6] clk: st: clk-flexgen: Detect " Lee Jones
2016-06-07 11:19 ` Lee Jones
2016-06-07 11:19 ` Lee Jones
2016-06-07 11:19 ` [PATCH 2/6] clk: st: clkgen-fsyn: " Lee Jones
2016-06-07 11:19 ` Lee Jones
2016-06-07 11:19 ` Lee Jones
2016-06-07 11:19 ` [PATCH 3/6] clk: st: clkgen-pll: " Lee Jones
2016-06-07 11:19 ` Lee Jones
2016-06-07 11:19 ` [PATCH 4/6] ARM: sti: stih407-family: Supply defines for CLOCKGEN A0 Lee Jones
2016-06-07 11:19 ` Lee Jones
2016-06-07 11:19 ` [PATCH 5/6] ARM: sti: stih410-clocks: Identify critical clocks Lee Jones
2016-06-07 11:19 ` Lee Jones
2016-06-07 11:19 ` [PATCH 6/6] spi: st-ssc4: Remove 'no clocking' hack Lee Jones
2016-06-07 11:19 ` Lee Jones
2016-06-07 15:17 ` Mark Brown
2016-06-07 15:17 ` Mark Brown
2016-06-30 20:52 ` Lee Jones [this message]
2016-06-30 20:52 ` Lee Jones
2016-06-30 20:52 ` Lee Jones
2016-07-01 9:59 ` Mark Brown
2016-07-01 9:59 ` Mark Brown
2016-06-30 19:23 ` [PATCH 0/6] clk: sti: Add support for critical clocks Stephen Boyd
2016-06-30 19:23 ` Stephen Boyd
2016-06-30 20:54 ` Lee Jones
2016-06-30 20:54 ` Lee Jones
2016-06-30 20:54 ` Lee Jones
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=20160630205215.GF1707@dell \
--to=lee.jones@linaro.org \
--cc=broonie@kernel.org \
--cc=kernel@stlinux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=maxime.coquelin@st.com \
--cc=mturquette@baylibre.com \
--cc=patrice.chotard@st.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 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.