From: k.kozlowski@samsung•com (Krzysztof Kozlowski)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v3 7/7] clk: exynos5433: remove CLK_IGNORE_UNUSED flag from SPI clocks
Date: Wed, 13 Jul 2016 11:54:52 +0200 [thread overview]
Message-ID: <57860FEC.3090004@samsung.com> (raw)
In-Reply-To: <578607FD.6050705@samsung.com>
On 07/13/2016 11:21 AM, Sylwester Nawrocki wrote:
> On 07/13/2016 12:17 AM, Michael Turquette wrote:
>>
>> Do you want these patches to go through same tree? If not, I can take
>> this patch into clk-next.
>
> I think this patch can safely go separately through the clk tree,
> we just need to ensure whole series is merged for same release
> to avoid regressions. There should be no problems with git bisect
> since there is no exynos5433 based board dts in mainline yet.
Ack.
Best regards,
Krzysztof
next prev parent reply other threads:[~2016-07-13 9:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 10:02 [PATCH v3 0/7] spi s3c64xx ioclk handling Andi Shyti
2016-07-12 10:02 ` [PATCH v3 1/7] bindings: spi-samsung: add exynos5433 spi compatible Andi Shyti
2016-07-14 16:25 ` Mark Brown
2016-07-16 20:26 ` Rob Herring
2016-07-12 10:02 ` [PATCH v3 2/7] bindings: spi-samsung: document the clocks and the clock-name property Andi Shyti
2016-07-16 20:30 ` Rob Herring
2016-07-18 10:30 ` Sylwester Nawrocki
2016-07-12 10:02 ` [PATCH v3 3/7] spi: s3c64xx: rename goto labels to meaningful names Andi Shyti
2016-07-12 10:02 ` [PATCH v3 4/7] spi: s3c64xx: use error code from clk_prepare_enable() Andi Shyti
2016-07-12 10:02 ` [PATCH v3 5/7] spi: s3c64xx: add Exynos5433 compatible for ioclk handling Andi Shyti
2016-07-12 10:02 ` [PATCH v3 6/7] spi: s3c64xx: restore removed comments Andi Shyti
2016-07-12 10:02 ` [PATCH v3 7/7] clk: exynos5433: remove CLK_IGNORE_UNUSED flag from SPI clocks Andi Shyti
2016-07-12 22:17 ` Michael Turquette
2016-07-13 2:08 ` Andi Shyti
2016-07-13 9:21 ` Sylwester Nawrocki
2016-07-13 9:54 ` Krzysztof Kozlowski [this message]
2016-07-13 12:44 ` Andi Shyti
2016-07-13 21:56 ` Michael Turquette
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=57860FEC.3090004@samsung.com \
--to=k.kozlowski@samsung$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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