linux-kernel - Re: [GIT PULL] PHY: For 5.6

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <c6b3e4fe-38ae-4c62-e54a-c56804338b0e@ti.com>
Date:   Fri, 17 Jan 2020 11:05:04 +0530
From:   Kishon Vijay Abraham I <kishon@...com>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC:     <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] PHY: For 5.6

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