public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Kishon Vijay Abraham I <kishon@ti.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL v2] PHY: for 5.2-rc
Date: Mon, 1 Jul 2019 12:14:15 +0200	[thread overview]
Message-ID: <20190701101415.GC23548@kroah.com> (raw)
In-Reply-To: <194c1b99-aff4-6118-b853-6745b306567f@ti.com>

On Thu, Jun 27, 2019 at 06:46:50PM +0530, Kishon Vijay Abraham I wrote:
> Hi Greg,
> 
> On 21/06/19 12:50 PM, Kishon Vijay Abraham I wrote:
> > 
> > 
> > On 21/06/19 12:10 PM, Greg Kroah-Hartman wrote:
> >> On Fri, Jun 21, 2019 at 11:41:26AM +0530, Kishon Vijay Abraham I wrote:
> >>> Hi Greg,
> >>>
> >>> On 12/06/19 3:57 PM, Kishon Vijay Abraham I wrote:
> >>>> Hi Greg,
> >>>>
> >>>> Please find the updated pull request for 5.2 -rc cycle. Here I dropped
> >>>> the patch that added "static" for a function to fix sparse warning.
> >>>>
> >>>> I'm also sending the patches along with this pull request in case you'd
> >>>> like to look them.
> >>>>
> >>>> Consider merging it in this -rc cycle and let me know if you want me
> >>>> to make any further changes.
> >>>
> >>> Are you planning to merge this?
> >>
> >> Ugh, fell through the cracks of my huge TODO mbox at the moment, sorry.
> >> It's still there, should get to it next week...
> > 
> > All right, thanks!
> 
> I think it's not merged yet. If you think it's too late, I can send it along
> with the merge window pull request.

Sorry for the delay, I've merged this into my branch for 5.3-rc1.  If
anything needed to go into 5.2, can you send the git commit ids to
stable@vger.kernel.org when they hit Linus's tree?

thanks,

greg k-h

  reply	other threads:[~2019-07-01 10:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-12 10:27 [GIT PULL v2] PHY: for 5.2-rc Kishon Vijay Abraham I
2019-06-12 10:27 ` [PATCH 1/6] phy: qcom-qusb2: fix missing assignment of ret when calling clk_prepare_enable Kishon Vijay Abraham I
2019-06-12 10:27 ` [PATCH 2/6] phy: renesas: rcar-gen2: Fix memory leak at error paths Kishon Vijay Abraham I
2019-06-12 10:28 ` [PATCH 3/6] phy: usb: phy-brcm-usb: Remove sysfs attributes upon driver removal Kishon Vijay Abraham I
2019-06-12 10:28 ` [PATCH 4/6] dt-bindings: phy: tegra-xusb: List PLL power supplies Kishon Vijay Abraham I
2019-06-12 10:28 ` [PATCH 5/6] phy: tegra: xusb: Add Tegra124 " Kishon Vijay Abraham I
2019-06-12 10:28 ` [PATCH 6/6] phy: tegra: xusb: Add Tegra210 " Kishon Vijay Abraham I
2019-06-21  6:11 ` [GIT PULL v2] PHY: for 5.2-rc Kishon Vijay Abraham I
2019-06-21  6:40   ` Greg Kroah-Hartman
2019-06-21  7:20     ` Kishon Vijay Abraham I
2019-06-27 13:16       ` Kishon Vijay Abraham I
2019-07-01 10:14         ` Greg Kroah-Hartman [this message]
2019-07-01 10:31           ` Kishon Vijay Abraham I
2019-07-01 13:06             ` Greg Kroah-Hartman

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=20190701101415.GC23548@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=kishon@ti.com \
    --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