devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shengjiu Wang <shengjiu.wang@freescale.com>
To: Michael Turquette <mturquette@baylibre.com>
Cc: shawnguo@kernel.org, kernel@pengutronix.de, robh+dt@kernel.org,
	pawel.moll@arm.com, mark.rutland@arm.com,
	ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
	linux@arm.linux.org.uk, sboyd@codeaurora.org,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org
Subject: Re: [PATCH V1 0/3] fix clock issue for fsl,spdif
Date: Wed, 26 Aug 2015 09:19:24 +0800	[thread overview]
Message-ID: <20150826011922.GA9708@shlinux2> (raw)
In-Reply-To: <20150825184527.31346.52324@quantum>

On Tue, Aug 25, 2015 at 11:45:27AM -0700, Michael Turquette wrote:
> Quoting Shengjiu Wang (2015-08-11 02:26:51)
> > fix clock issue for fsl,spdif
> > 
> > Shengjiu Wang (3):
> >   ARM: imx6q: Add SPDIF_GCLK clock in clock tree
> >   ARM: imx6sl: Add SPDIF_GCLK clock in clock tree
> >   ARM: imx6sx: Add SPDIF_GCLK clock in clock tree
> 
> Hello Shengjiu Wang,
> 
> Please move the dts changes into separate patches. I can take the
> changes to the clock driver and the header through the clk tree, but the
> dt patches need to go through arm-soc.
> 
> Regards,
> Mike

Thanks Mike. I will send another patches for dts changes.

> 
> > 
> >  arch/arm/boot/dts/imx6qdl.dtsi            |  2 +-
> >  arch/arm/boot/dts/imx6sl.dtsi             | 16 ++++++++++++++++
> >  arch/arm/boot/dts/imx6sx.dtsi             |  2 +-
> >  drivers/clk/imx/clk-imx6q.c               |  4 +++-
> >  drivers/clk/imx/clk-imx6sl.c              |  4 +++-
> >  drivers/clk/imx/clk-imx6sx.c              |  1 +
> >  include/dt-bindings/clock/imx6qdl-clock.h |  3 ++-
> >  include/dt-bindings/clock/imx6sl-clock.h  |  3 ++-
> >  include/dt-bindings/clock/imx6sx-clock.h  |  3 ++-
> >  9 files changed, 31 insertions(+), 7 deletions(-)
> > 
> > -- 
> > 1.9.1
> > 
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at  http://www.tux.org/lkml/

      reply	other threads:[~2015-08-26  1:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-11  9:26 [PATCH V1 0/3] fix clock issue for fsl,spdif Shengjiu Wang
2015-08-11  9:26 ` [PATCH V1 1/3] ARM: imx6q: Add SPDIF_GCLK clock in clock tree Shengjiu Wang
2015-08-11  9:26 ` [PATCH V1 2/3] ARM: imx6sl: " Shengjiu Wang
2015-08-11  9:26 ` [PATCH V1 3/3] ARM: imx6sx: " Shengjiu Wang
     [not found] ` <cover.1439284957.git.shengjiu.wang-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2015-08-25 18:45   ` [PATCH V1 0/3] fix clock issue for fsl,spdif Michael Turquette
2015-08-26  1:19     ` Shengjiu Wang [this message]

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=20150826011922.GA9708@shlinux2 \
    --to=shengjiu.wang@freescale.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=mturquette@baylibre.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@codeaurora.org \
    --cc=shawnguo@kernel.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 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).