public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kishon Vijay Abraham I <kishon@ti.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] phy: for 4.12 -rc
Date: Mon, 22 May 2017 19:19:18 +0530	[thread overview]
Message-ID: <bbe98454-2156-b886-a765-e877d2ab78ae@ti.com> (raw)
In-Reply-To: <20170522133838.GA6863@kroah.com>

Hi,

On Monday 22 May 2017 07:08 PM, Greg Kroah-Hartman wrote:
> On Mon, May 22, 2017 at 04:28:24PM +0530, Kishon Vijay Abraham I wrote:
>> Hi Greg,
>>
>> On Monday 22 May 2017 03:56 PM, Greg Kroah-Hartman wrote:
>>> On Fri, May 19, 2017 at 08:13:27PM +0530, Kishon Vijay Abraham I wrote:
>>>> Hi Greg,
>>>>
>>>> Please find the pull request for 4.12 -rc below.
>>>>
>>>> Here we move all the phy drivers to vendor specific directories (so that it's
>>>> easier to manage) and a couple of fixes in phy-qcom-qmp driver.
>>>
>>> Wait, why do this so late in the review cycle?  This isn't a -rc3 fix,
>>> it's a -rc1 change.  I can't take this now at all, sorry.
>>>
>>> I could take it during the -rc1 merge window, that would have been a
>>> good time for it, like the last few days of it?  How about doing that
>>> the next time?
>>
>> I thought immediately after -rc1 would be a good time when no new phy drivers
>> would be added.
> 
> You sent it to me on Friday, after rc1 was released on Saturday, that's
> almost a full week after what I would think "immediately" would be :)

yeah, I should have sent it earlier :-(

-Kishon

      reply	other threads:[~2017-05-22 13:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-19 14:43 [GIT PULL] phy: for 4.12 -rc Kishon Vijay Abraham I
2017-05-22 10:26 ` Greg Kroah-Hartman
2017-05-22 10:58   ` Kishon Vijay Abraham I
2017-05-22 13:38     ` Greg Kroah-Hartman
2017-05-22 13:49       ` Kishon Vijay Abraham I [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=bbe98454-2156-b886-a765-e877d2ab78ae@ti.com \
    --to=kishon@ti.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.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