From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] i.MX clock fixes for 4.6, take 2
Date: Wed, 11 May 2016 11:40:23 -0700 [thread overview]
Message-ID: <20160511184023.GE3492@codeaurora.org> (raw)
In-Reply-To: <20160511121512.GP5874@tiger>
On 05/11, Shawn Guo wrote:
> On Fri, May 06, 2016 at 11:02:17AM -0700, Stephen Boyd wrote:
> > On 05/03, Shawn Guo wrote:
> > > The following changes since commit 7196c52c9377df0175b510ff5896bda524f7345e:
> > >
> > > clk: imx6q: fix typo in CAN clock definition (2016-04-13 15:27:15 +0800)
> > >
> > > are available in the git repository at:
> > >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-clk-fixes-4.6-2
> > >
> > > for you to fetch changes up to 3397c2c45b1b6f54834dfeae30a73046f33ca943:
> > >
> > > ARM: dts: imx35: restore existing used clock enumeration (2016-04-18 12:37:21 +0800)
> > >
> > > ----------------------------------------------------------------
> > > The i.MX clock fixes for 4.6, take 2:
> > > - Fix the commit 3713e3f5e927 ("clk: imx35: define two clocks for rtc")
> > > which messed up the clock enumeration when adding new clock.
> >
> > This commit wasn't introduced in this merge window, so I'm going
> > to pull this into clk-next unless you have some justification.
>
> That's fine. Thanks, Stephen.
Thanks. Pulled into clk-next.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2016-05-11 18:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 13:36 [GIT PULL] i.MX clock fixes for 4.6, take 2 Shawn Guo
2016-05-06 18:02 ` Stephen Boyd
2016-05-11 12:15 ` Shawn Guo
2016-05-11 18:40 ` Stephen Boyd [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=20160511184023.GE3492@codeaurora.org \
--to=sboyd@codeaurora.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).