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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 20 Nov 2020 15:41:38 +0530
From:   Vinod Koul <>
To:     Marek Szyprowski <>
        Jaehoon Chung <>,
        Jingoo Han <>,
        Krzysztof Kozlowski <>,
        Bjorn Helgaas <>,
        Lorenzo Pieralisi <>,
        Kishon Vijay Abraham I <>,
        Rob Herring <>,
        Bartlomiej Zolnierkiewicz <>
Subject: Re: [PATCH v4 4/5] phy: samsung: phy-exynos-pcie: rework driver to
 support Exynos5433 PCIe PHY

On 20-11-20, 10:58, Marek Szyprowski wrote:
> Hi Vinod,
> On 20.11.2020 10:41, Vinod Koul wrote:
> > On 13-11-20, 18:01, Marek Szyprowski wrote:
> >> From: Jaehoon Chung <>
> >>
> >> Exynos5440 SoC support has been dropped since commit 8c83315da1cf ("ARM:
> >> dts: exynos: Remove Exynos5440"). Rework this driver to support PCIe PHY
> >> variant found in the Exynos5433 SoCs.
> > I am expecting this series to go thru PCI tree, so:
> >
> > Acked-By: Vinod Koul <>
> Frankly, the PHY driver can also go via PHY tree without causing any 
> issue. The old driver is not used at all, so there is no runtime 
> dependency. This will help avoiding the merge conflict: yesterday I've 
> noticed that this patch conflicts with the commit 2f0c9fac3be6 ("phy: 
> samsung: convert to devm_platform_ioremap_resource") in phy-next. The 
> resolution is simple (use all the code from the new driver), but if 
> needed I can resend the PHY driver after a rebase onto the current next 
> tree.

Okay do send me the rebase patch


Powered by blists - more mailing lists