linux-clk.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tero Kristo <t-kristo@ti.com>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: Mike Turquette <mturquette@baylibre.com>,
	"tony@atomide.com" <tony@atomide.com>,
	Paul Walmsley <paul@pwsan.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	<linux-clk@vger.kernel.org>
Subject: Re: [GIT PULL] clk: ti: clock driver code migration to drivers
Date: Wed, 15 Jul 2015 14:44:08 +0300	[thread overview]
Message-ID: <55A64788.6000206@ti.com> (raw)
In-Reply-To: <55A57195.80609@codeaurora.org>

On 07/14/2015 11:31 PM, Stephen Boyd wrote:
> On 07/14/2015 01:09 PM, Tero Kristo wrote:
>> On 07/14/2015 10:29 PM, Stephen Boyd wrote:
>>> On 07/14/2015 01:54 AM, Tero Kristo wrote:
>>>> The following changes since commit
>>>> bc0195aad0daa2ad5b0d76cce22b167bc3435590:
>>>>
>>>>   Linux 4.2-rc2 (2015-07-12 15:10:30 -0700)
>>>
>>> Why did this get rebased onto v4.2-rc2? I thought it was all ready to go
>>> based on v4.1-rc2? If possible leave it on v4.1-rc2 please.
>>
>> You mean 4.2-rc1 I guess...? Or do you really mean the old 4.1-rc2....?
>
> Old 4.1-rc2 please
>

Ok, posting a new one after this, this one can be ignored.

-Tero

      reply	other threads:[~2015-07-15 11:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-14  8:54 [GIT PULL] clk: ti: clock driver code migration to drivers Tero Kristo
2015-07-14  9:54 ` Tony Lindgren
2015-07-14 10:32   ` Tero Kristo
2015-07-14 10:40     ` Tony Lindgren
2015-07-16  1:51       ` Paul Walmsley
2015-07-16  6:02         ` Tero Kristo
2015-07-24  0:37       ` Michael Turquette
2015-07-14 19:29 ` Stephen Boyd
2015-07-14 20:09   ` Tero Kristo
2015-07-14 20:31     ` Stephen Boyd
2015-07-15 11:44       ` Tero Kristo [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=55A64788.6000206@ti.com \
    --to=t-kristo@ti.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=paul@pwsan.com \
    --cc=sboyd@codeaurora.org \
    --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;
as well as URLs for NNTP newsgroup(s).