From: shawn.guo@freescale.com (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: clk-imx6sl: correct the pxp and epdc axi clock selections
Date: Fri, 5 Sep 2014 08:43:23 +0800 [thread overview]
Message-ID: <20140905004322.GE10809@dragon> (raw)
In-Reply-To: <1409819592-31462-1-git-send-email-chen.fang@freescale.com>
On Thu, Sep 04, 2014 at 04:33:12PM +0800, Fancy Fang wrote:
> The parent clocks of IMX6SL_CLK_PXP_AXI_SEL and IMX6SL_CLK_EPDC_AXI_SEL
> clocks are not the same. So split the epdc_pxp_sels into two different
> clock selections 'pxp_axi_sels' and 'epdc_axi_sels'.
>
> Signed-off-by: Fancy Fang <chen.fang@freescale.com>
> Signed-off-by: Robby Cai <R63905@freescale.com>
Applied, thanks.
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawn.guo@freescale.com>
To: Fancy Fang <chen.fang@freescale.com>
Cc: <linux-arm-kernel@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: clk-imx6sl: correct the pxp and epdc axi clock selections
Date: Fri, 5 Sep 2014 08:43:23 +0800 [thread overview]
Message-ID: <20140905004322.GE10809@dragon> (raw)
In-Reply-To: <1409819592-31462-1-git-send-email-chen.fang@freescale.com>
On Thu, Sep 04, 2014 at 04:33:12PM +0800, Fancy Fang wrote:
> The parent clocks of IMX6SL_CLK_PXP_AXI_SEL and IMX6SL_CLK_EPDC_AXI_SEL
> clocks are not the same. So split the epdc_pxp_sels into two different
> clock selections 'pxp_axi_sels' and 'epdc_axi_sels'.
>
> Signed-off-by: Fancy Fang <chen.fang@freescale.com>
> Signed-off-by: Robby Cai <R63905@freescale.com>
Applied, thanks.
next prev parent reply other threads:[~2014-09-05 0:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 8:33 [PATCH] ARM: clk-imx6sl: correct the pxp and epdc axi clock selections Fancy Fang
2014-09-04 8:33 ` Fancy Fang
2014-09-05 0:43 ` Shawn Guo [this message]
2014-09-05 0:43 ` Shawn Guo
-- strict thread matches above, loose matches on Subject: below --
2014-09-04 8:28 Fancy Fang
2014-09-04 8:28 ` Fancy Fang
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=20140905004322.GE10809@dragon \
--to=shawn.guo@freescale.com \
--cc=linux-arm-kernel@lists.infradead.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.