From: Leela Krishna Amudala <l.krishna@samsung.com>
To: Wim Van Sebroeck <wim@iguana.be>, Kukjin Kim <kgene.kim@samsung.com>
Cc: "linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
"dianders@chromium.org" <dianders@chromium.org>,
Tomasz Figa <t.figa@samsung.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>,
"cpgs ." <cpgs@samsung.com>,
"linux@roeck-us.net" <linux@roeck-us.net>
Subject: Re: Re: [PATCH V12 1/3] ARM: dts: Add pmu sysreg node to exynos5250 and exynos5420 dtsi files
Date: Fri, 10 Jan 2014 07:55:39 +0000 (GMT) [thread overview]
Message-ID: <3783504.439671389340538922.JavaMail.weblogic@epv6ml10> (raw)
Hi Wim,
I rebased this patch series on Kukjin's for-next branch.
That is the reason for missing this context code in the patch.
As this is a dts file change and if Kukjin accepts to merge this patch
into your "linux-watchdog-next" tree you can rebase and apply it.
Best Wishes,
Leela Krishna.
------- Original Message -------
Sender : Wim Van Sebroeck<wim@iguana.be>
Date : Jan 10, 2014 13:11 (GMT+05:30)
Title : Re: [PATCH V12 1/3] ARM: dts: Add pmu sysreg node to exynos5250 and exynos5420 dtsi files
Hi Leela,
> This patch adds pmusysreg node to exynos5250 and exynos5420 dtsi files to
> handle PMU register accesses in a centralized way using syscon driver
>
> Signed-off-by: Leela Krishna Amudala
> Reviewed-by: Tomasz Figa
> Reviewed-by: Doug Anderson
> Tested-by: Doug Anderson
> ---
...
> diff --git a/arch/arm/boot/dts/exynos5420.dtsi b/arch/arm/boot/dts/exynos5420.dtsi
> index b1fa334..cd47db0 100644
> --- a/arch/arm/boot/dts/exynos5420.dtsi
> +++ b/arch/arm/boot/dts/exynos5420.dtsi
> @@ -402,4 +402,9 @@
> clock-names = "gscl";
> samsung,power-domain = <&gsc_pd>;
> };
I can't add this patch since there is no "gscl" in the current linux-tree.
Is this depending on another patch or are we going to fix this in another way?
Kind regards,
Wim.
Best Wishes,
Leela Krishna.
reply other threads:[~2014-01-10 7:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3783504.439671389340538922.JavaMail.weblogic@epv6ml10 \
--to=l.krishna@samsung.com \
--cc=cpgs@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=kgene.kim@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=t.figa@samsung.com \
--cc=wim@iguana.be \
/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;
as well as URLs for NNTP newsgroup(s).