From: Stephen Boyd <sboyd@codeaurora.org>
To: Tony Lindgren <tony@atomide.com>
Cc: Tero Kristo <t-kristo@ti.com>,
Michael Turquette <mturquette@baylibre.com>,
linux-clk <linux-clk@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [GIT PULL] clk: ti: cleanups for 4.12 merge window
Date: Tue, 4 Apr 2017 18:26:49 -0700 [thread overview]
Message-ID: <20170405012649.GI18246@codeaurora.org> (raw)
In-Reply-To: <20170404161413.GT10760@atomide.com>
On 04/04, Tony Lindgren wrote:
> * Tero Kristo <t-kristo@ti.com> [170317 05:55]:
> > Hi Stephen/Mike,
> >
> > This is basically the TI clock driver cleanup series v2 posted last week,
> > sending a pull request now as there hasn't been any additional comments.
> >
> > -Tero
> >
> > ==================================================================
> >
> > The following changes since commit c1ae3cfa0e89fa1a7ecc4c99031f5e9ae99d9201:
> >
> > Linux 4.11-rc1 (2017-03-05 12:59:56 -0800)
> >
> > are available in the git repository at:
> >
> > https://github.com/t-kristo/linux-pm.git for-4.12-ti-clk-cleanups
> >
> > for you to fetch changes up to 6c0afb503937a12a8d20a805fcf263e31afa9871:
> >
> > clk: ti: convert to use proper register definition for all accesses
> > (2017-03-08 13:06:15 +0200)
>
> Any news on getting this merged?
>
Pulled into clk-next. Sorry for the slowness, I've been pulled
into some other work recently and also took a spring break
vacation last week so I'm just getting back to clk stuff.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-04-05 1:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-17 12:53 [GIT PULL] clk: ti: cleanups for 4.12 merge window Tero Kristo
2017-04-04 16:14 ` Tony Lindgren
2017-04-05 1:26 ` Stephen Boyd [this message]
2017-04-05 13:41 ` Tony Lindgren
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=20170405012649.GI18246@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=t-kristo@ti.com \
--cc=tony@atomide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox