From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Alim Akhtar <alim.akhtar@samsung.com>
Cc: linux-arm-kernel@lists.infradead.org, thomas.ab@samsung.com,
k.kozlowski@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: Enable clocks for CMU_CCORE and CMU_FSYS0 blocks
Date: Tue, 12 Apr 2016 13:37:19 +0200 [thread overview]
Message-ID: <570CDDEF.8090401@samsung.com> (raw)
In-Reply-To: <1460459243-27120-1-git-send-email-alim.akhtar@samsung.com>
On 04/12/2016 01:07 PM, Alim Akhtar wrote:
> This patch enables clocks for CMU_CCORE and CMU_FSYS0 blocks. This is
> required before accessing registers of these blocks.
Patch applied, thanks!
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: Enable clocks for CMU_CCORE and CMU_FSYS0 blocks
Date: Tue, 12 Apr 2016 13:37:19 +0200 [thread overview]
Message-ID: <570CDDEF.8090401@samsung.com> (raw)
In-Reply-To: <1460459243-27120-1-git-send-email-alim.akhtar@samsung.com>
On 04/12/2016 01:07 PM, Alim Akhtar wrote:
> This patch enables clocks for CMU_CCORE and CMU_FSYS0 blocks. This is
> required before accessing registers of these blocks.
Patch applied, thanks!
next prev parent reply other threads:[~2016-04-12 11:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-12 11:07 [PATCH] clk: samsung: exynos7: Enable clocks for CMU_CCORE and CMU_FSYS0 blocks Alim Akhtar
2016-04-12 11:07 ` Alim Akhtar
2016-04-12 11:37 ` Sylwester Nawrocki [this message]
2016-04-12 11:37 ` Sylwester Nawrocki
2016-04-13 6:26 ` Tomasz Figa
2016-04-13 6:26 ` Tomasz Figa
2016-04-13 10:36 ` Sylwester Nawrocki
2016-04-13 10:36 ` Sylwester Nawrocki
2016-04-13 11:31 ` Tomasz Figa
2016-04-13 11:31 ` Tomasz Figa
2016-04-13 11:54 ` Alim Akhtar
2016-04-13 11:54 ` Alim Akhtar
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=570CDDEF.8090401@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.