From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Alim Akhtar <alim.akhtar@samsung.com>
Cc: Krzysztof Kozlowski <k.kozlowski@samsung.com>,
linux-arm-kernel@lists.infradead.org, thomas.ab@samsung.com,
linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
linux-clk@vger.kernel.org, sboyd@codeaurora.org,
mturquette@baylibre.com, tomasz.figa@gmail.com
Subject: Re: [PATCH] clk: samsung: exynos7: Don't gate CMU_{CCORE, FSYS0} blocks clock
Date: Wed, 25 May 2016 12:49:02 +0200 [thread overview]
Message-ID: <5745831E.2060004@samsung.com> (raw)
In-Reply-To: <57454054.1010001@samsung.com>
Hi Alim,
On 05/25/2016 08:04 AM, Alim Akhtar wrote:
> Looks like this patch is not available on your tree.
Thanks for the reminder, I'll apply it next week, after 3.7-rc1 is released.
--
Regards,
Sylwester
WARNING: multiple messages have this Message-ID (diff)
From: s.nawrocki@samsung.com (Sylwester Nawrocki)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: samsung: exynos7: Don't gate CMU_{CCORE, FSYS0} blocks clock
Date: Wed, 25 May 2016 12:49:02 +0200 [thread overview]
Message-ID: <5745831E.2060004@samsung.com> (raw)
In-Reply-To: <57454054.1010001@samsung.com>
Hi Alim,
On 05/25/2016 08:04 AM, Alim Akhtar wrote:
> Looks like this patch is not available on your tree.
Thanks for the reminder, I'll apply it next week, after 3.7-rc1 is released.
--
Regards,
Sylwester
next prev parent reply other threads:[~2016-05-25 10:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 4:42 [PATCH] clk: samsung: exynos7: Don't gate CMU_{CCORE, FSYS0} blocks clock Alim Akhtar
2016-04-14 4:42 ` Alim Akhtar
2016-04-14 7:50 ` Krzysztof Kozlowski
2016-04-14 7:50 ` Krzysztof Kozlowski
2016-04-15 12:37 ` Alim Akhtar
2016-04-15 12:37 ` Alim Akhtar
2016-04-15 16:34 ` Sylwester Nawrocki
2016-04-15 16:34 ` Sylwester Nawrocki
2016-05-25 6:04 ` Alim Akhtar
2016-05-25 6:04 ` Alim Akhtar
2016-05-25 10:49 ` Sylwester Nawrocki [this message]
2016-05-25 10:49 ` Sylwester Nawrocki
2016-05-30 12:50 ` Sylwester Nawrocki
2016-05-30 12:50 ` Sylwester Nawrocki
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=5745831E.2060004@samsung.com \
--to=s.nawrocki@samsung.com \
--cc=alim.akhtar@samsung.com \
--cc=k.kozlowski@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.org \
--cc=thomas.ab@samsung.com \
--cc=tomasz.figa@gmail.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.