mirror of https://lore.kernel.org/lkml/
 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>
Subject: Re: [GIT PULL] PHY: For 5.6
Date: Fri, 17 Jan 2020 11:05:04 +0530	[thread overview]
Message-ID: <c6b3e4fe-38ae-4c62-e54a-c56804338b0e@ti.com> (raw)
In-Reply-To: <20200116195524.GA1096827@kroah.com>

Hi Greg,

On 17/01/20 1:25 AM, Greg Kroah-Hartman wrote:
> On Thu, Jan 16, 2020 at 04:35:15PM +0530, Kishon Vijay Abraham I wrote:
>> Hi Greg,
>>
>> Please find the pull request for 5.6 merge window below.
>>
>> PHY core now creates a device link between PHY consumer and PHY
>> provider required for suspend/resume ordering and also adds support
>> for DisplayPort controller to pass configuration parameters to PHY.
>>
>> It includes new PHY drivers for TI's J721E SoC (PCIe and USB), eMMC
>> PHY driver for Intel's LGM SoC and USB PHY driver for Broadcom
>> SoC.
>>
>> For the detailed list of changes, please see the tag message below.
>> All these changes have been in linux -next for a while now.
>> Consider merging this for the next merge window and let me know if I
>> have to change something.
> 
> I got the following warning, which linux-next should also reported:
> Commit: 56b337ef505d ("phy: ti: j721e-wiz: Fix return value check in wiz_probe()")
> 	Fixes tag: Fixes: b46f531313a4 ("phy: ti: j721e-wiz: Add support for WIZ module present in TI J721E SoC")
> 	Has these problem(s):
> 	        - Target SHA1 does not exist
> 
> Maybe I am merging into the wrong tree?
> 
> Anyway, I'll take this, hopefully that id shows up somewhere :)

Looks like this is a real issue as I might have not updated the commit
ID in Fixes tag after a rebase. Not sure why linux-next didn't report
this. Anyways I'll fix that up and send a new Pull Request.

Thanks
Kishon

      reply	other threads:[~2020-01-17  5:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-16 11:05 Kishon Vijay Abraham I
2020-01-16 19:55 ` Greg Kroah-Hartman
2020-01-17  5:35   ` 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=c6b3e4fe-38ae-4c62-e54a-c56804338b0e@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

all inboxes | Powered by JetHome®