From: Shawn Guo <shawnguo@kernel.org>
To: Michael Turquette <mturquette@baylibre.com>
Cc: kernel@pengutronix.de, Stephen Boyd <sboyd@codeaurora.org>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] i.MX clock updates for 4.2
Date: Wed, 12 Aug 2015 10:34:57 +0800 [thread overview]
Message-ID: <20150812023456.GC10035@tiger> (raw)
In-Reply-To: <20150811174657.2416.1270@quantum>
On Tue, Aug 11, 2015 at 10:46:57AM -0700, Michael Turquette wrote:
> Hi Shawn,
>
> Quoting Shawn Guo (2015-08-11 01:59:21)
> > Hi Michael, Stephen,
> >
> > The i.MX clock drivers were moved into drivers/clk/imx folder since
> > v4.2-rc1, so I would like to send i.MX clock changes through clock tree
> > from this cycle. Here is my first pull request to you guys. I'm using
> > signed tags, same as how I work with arm-soc folks. Let me know if
> > there is any problem with it.
>
> Everything looks good. Pulled.
Thanks, Mike.
>
> >
> > Also, please keep it stable, because I need to pull it into other
> > branch as dependency which I will send via arm-soc tree.
>
> Will do.
>
> Also, the clock driver was not Cc'd to linux-clk mailing list nor did it
> Cc myself or Stephen. I've taken a quick look at it and it seems fine,
> but please post clk patches to the linux-clk mailing list in the future.
I will ensure that all i.MX clock patches get Cc'd to linux-clk and you
guys in the future.
Shawn
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] i.MX clock updates for 4.2
Date: Wed, 12 Aug 2015 10:34:57 +0800 [thread overview]
Message-ID: <20150812023456.GC10035@tiger> (raw)
In-Reply-To: <20150811174657.2416.1270@quantum>
On Tue, Aug 11, 2015 at 10:46:57AM -0700, Michael Turquette wrote:
> Hi Shawn,
>
> Quoting Shawn Guo (2015-08-11 01:59:21)
> > Hi Michael, Stephen,
> >
> > The i.MX clock drivers were moved into drivers/clk/imx folder since
> > v4.2-rc1, so I would like to send i.MX clock changes through clock tree
> > from this cycle. Here is my first pull request to you guys. I'm using
> > signed tags, same as how I work with arm-soc folks. Let me know if
> > there is any problem with it.
>
> Everything looks good. Pulled.
Thanks, Mike.
>
> >
> > Also, please keep it stable, because I need to pull it into other
> > branch as dependency which I will send via arm-soc tree.
>
> Will do.
>
> Also, the clock driver was not Cc'd to linux-clk mailing list nor did it
> Cc myself or Stephen. I've taken a quick look at it and it seems fine,
> but please post clk patches to the linux-clk mailing list in the future.
I will ensure that all i.MX clock patches get Cc'd to linux-clk and you
guys in the future.
Shawn
next prev parent reply other threads:[~2015-08-12 2:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 8:59 [GIT PULL] i.MX clock updates for 4.2 Shawn Guo
2015-08-11 8:59 ` Shawn Guo
2015-08-11 17:46 ` Michael Turquette
2015-08-11 17:46 ` Michael Turquette
2015-08-11 18:34 ` Stephen Boyd
2015-08-11 18:34 ` Stephen Boyd
2015-08-12 2:36 ` Shawn Guo
2015-08-12 2:36 ` Shawn Guo
2015-08-12 2:34 ` Shawn Guo [this message]
2015-08-12 2:34 ` Shawn Guo
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=20150812023456.GC10035@tiger \
--to=shawnguo@kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.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.