From: Herbert Xu <herbert@gondor.apana.org.au>
To: javier Martin <javier.martin@vista-silicon.com>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
linux-crypto@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org, davem@davemloft.net,
kernel@pengutronix.de, gcembed@gmail.com, shawn.guo@linaro.org,
arnd@arndb.de, swarren@nvidia.com
Subject: Re: [PATCH v3 1/2] i.MX27: Add clock support for SAHARA2.
Date: Sun, 10 Mar 2013 16:34:01 +0800 [thread overview]
Message-ID: <20130310083401.GB10448@gondor.apana.org.au> (raw)
In-Reply-To: <CACKLOr2kuWXMreEFA4wqyYVRNnPwmEoHPM2+V+tN5P_1bQ+iJQ@mail.gmail.com>
On Tue, Mar 05, 2013 at 08:48:19AM +0100, javier Martin wrote:
> Hi Sascha,
>
> On 4 March 2013 08:53, Sascha Hauer <s.hauer@pengutronix.de> wrote:
> > On Fri, Mar 01, 2013 at 12:37:52PM +0100, Javier Martin wrote:
> >>
> >> Signed-off-by: Javier Martin <javier.martin@vista-silicon.com>
> >> ---
> >> arch/arm/mach-imx/clk-imx27.c | 2 ++
> >> 1 file changed, 2 insertions(+)
> >>
> >> diff --git a/arch/arm/mach-imx/clk-imx27.c b/arch/arm/mach-imx/clk-imx27.c
> >> index 4c1d1e4..0b9664a 100644
> >> --- a/arch/arm/mach-imx/clk-imx27.c
> >> +++ b/arch/arm/mach-imx/clk-imx27.c
> >> @@ -253,6 +253,8 @@ int __init mx27_clocks_init(unsigned long fref)
> >> clk_register_clkdev(clk[nfc_baud_gate], NULL, "imx27-nand.0");
> >> clk_register_clkdev(clk[vpu_baud_gate], "per", "coda-imx27.0");
> >> clk_register_clkdev(clk[vpu_ahb_gate], "ahb", "coda-imx27.0");
> >> + clk_register_clkdev(clk[sahara_ahb_gate], "ahb", "sahara-imx27.0");
> >> + clk_register_clkdev(clk[sahara_ipg_gate], "ipg", "sahara-imx27.0");
> >
> > One of the first patches I want to push upstream for the next merge
> > window is this one:
> >
> > https://patchwork.kernel.org/patch/1817741/
> >
> > So the change above becomes unnecessary
>
> Very good. Then this patch can be safely dropped.
So should I take this patch or not?
Thanks,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
WARNING: multiple messages have this Message-ID (diff)
From: herbert@gondor.apana.org.au (Herbert Xu)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/2] i.MX27: Add clock support for SAHARA2.
Date: Sun, 10 Mar 2013 16:34:01 +0800 [thread overview]
Message-ID: <20130310083401.GB10448@gondor.apana.org.au> (raw)
In-Reply-To: <CACKLOr2kuWXMreEFA4wqyYVRNnPwmEoHPM2+V+tN5P_1bQ+iJQ@mail.gmail.com>
On Tue, Mar 05, 2013 at 08:48:19AM +0100, javier Martin wrote:
> Hi Sascha,
>
> On 4 March 2013 08:53, Sascha Hauer <s.hauer@pengutronix.de> wrote:
> > On Fri, Mar 01, 2013 at 12:37:52PM +0100, Javier Martin wrote:
> >>
> >> Signed-off-by: Javier Martin <javier.martin@vista-silicon.com>
> >> ---
> >> arch/arm/mach-imx/clk-imx27.c | 2 ++
> >> 1 file changed, 2 insertions(+)
> >>
> >> diff --git a/arch/arm/mach-imx/clk-imx27.c b/arch/arm/mach-imx/clk-imx27.c
> >> index 4c1d1e4..0b9664a 100644
> >> --- a/arch/arm/mach-imx/clk-imx27.c
> >> +++ b/arch/arm/mach-imx/clk-imx27.c
> >> @@ -253,6 +253,8 @@ int __init mx27_clocks_init(unsigned long fref)
> >> clk_register_clkdev(clk[nfc_baud_gate], NULL, "imx27-nand.0");
> >> clk_register_clkdev(clk[vpu_baud_gate], "per", "coda-imx27.0");
> >> clk_register_clkdev(clk[vpu_ahb_gate], "ahb", "coda-imx27.0");
> >> + clk_register_clkdev(clk[sahara_ahb_gate], "ahb", "sahara-imx27.0");
> >> + clk_register_clkdev(clk[sahara_ipg_gate], "ipg", "sahara-imx27.0");
> >
> > One of the first patches I want to push upstream for the next merge
> > window is this one:
> >
> > https://patchwork.kernel.org/patch/1817741/
> >
> > So the change above becomes unnecessary
>
> Very good. Then this patch can be safely dropped.
So should I take this patch or not?
Thanks,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2013-03-10 8:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 11:37 [PATCH v3 0/2] crypto: sahara: Add support for SAHARA in i.MX27 Javier Martin
2013-03-01 11:37 ` Javier Martin
2013-03-01 11:37 ` [PATCH v3 1/2] i.MX27: Add clock support for SAHARA2 Javier Martin
2013-03-01 11:37 ` Javier Martin
2013-03-04 7:53 ` Sascha Hauer
2013-03-04 7:53 ` Sascha Hauer
2013-03-05 7:48 ` javier Martin
2013-03-05 7:48 ` javier Martin
2013-03-10 8:34 ` Herbert Xu [this message]
2013-03-10 8:34 ` Herbert Xu
2013-03-10 23:08 ` Sascha Hauer
2013-03-10 23:08 ` Sascha Hauer
2013-03-11 1:19 ` Herbert Xu
2013-03-11 1:19 ` Herbert Xu
2013-03-11 7:42 ` Sascha Hauer
2013-03-11 7:42 ` Sascha Hauer
2013-03-11 8:04 ` javier Martin
2013-03-11 8:04 ` javier Martin
2013-03-01 11:37 ` [PATCH v3 2/2] crypto: sahara: Add driver for SAHARA2 accelerator Javier Martin
2013-03-01 11:37 ` Javier Martin
2013-03-19 9:43 ` javier Martin
2013-03-19 9:43 ` javier Martin
2013-03-21 9:53 ` Herbert Xu
2013-03-21 9:53 ` Herbert Xu
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=20130310083401.GB10448@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=gcembed@gmail.com \
--cc=javier.martin@vista-silicon.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawn.guo@linaro.org \
--cc=swarren@nvidia.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.