linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] clk: imx6sll: add GPIO LPCGs
Date: Thu, 12 Jul 2018 10:25:46 +0800	[thread overview]
Message-ID: <20180712022544.GP6959@dragon> (raw)
In-Reply-To: <153132682598.143105.16881098765923078751@swboyd.mtv.corp.google.com>

On Wed, Jul 11, 2018 at 09:33:45AM -0700, Stephen Boyd wrote:
> Quoting Shawn Guo (2018-07-11 01:43:03)
> > On Fri, Jul 06, 2018 at 01:58:46PM -0700, Stephen Boyd wrote:
> > > Quoting Anson Huang (2018-06-21 23:32:33)
> > > > According to Reference Manual Rev.0, 06/2017,
> > > > there are GPIO LPCGs defined in CCM CCGRs,
> > > > add them into clock tree.
> > > > 
> > > > Signed-off-by: Anson Huang <Anson.Huang@nxp.com>
> > > > ---
> > > 
> > > Applied to clk-next
> > 
> > Stephen,
> > 
> > If you can apply this patch to topic branch 'clk-imx-gpio-gates', I will
> > be able to pick up patch #2 for this cycle.
> 
> Can you merge in clk-imx6sll-gpio topic branch to your tree? I'm making
> topics for all patch series, so that's why this got stuck into a
> different topic branch.

Ah, okay.  I thought you apply patches directly to clk-next, and make
topic branches only for those having dependencies involved.

For future DT patches depending on clk ones, I will check clk tree and
merge corresponding topic branch to resolve dependency.

Thanks for clarifying.

Shawn

      reply	other threads:[~2018-07-12  2:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-22  6:32 [PATCH 1/2] clk: imx6sll: add GPIO LPCGs Anson Huang
2018-06-22  6:32 ` [PATCH 2/2] ARM: dts: imx6sll: add gpio clocks Anson Huang
2018-06-23 15:49   ` Fabio Estevam
2018-07-12  2:52   ` Shawn Guo
2018-08-29  1:12     ` Anson Huang
2018-08-29 14:30       ` Shawn Guo
2018-06-23 15:48 ` [PATCH 1/2] clk: imx6sll: add GPIO LPCGs Fabio Estevam
2018-07-03 19:31 ` Rob Herring
2018-07-06 20:58 ` Stephen Boyd
2018-07-11  8:43   ` Shawn Guo
2018-07-11 16:33     ` Stephen Boyd
2018-07-12  2:25       ` Shawn Guo [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=20180712022544.GP6959@dragon \
    --to=shawnguo@kernel.org \
    --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 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).