linux-kernel - Re: linux-next: duplicate patches in the phy-next tree

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <Y8jpFw5mfvyRLX/C@kroah.com>
Date:   Thu, 19 Jan 2023 07:54:15 +0100
From:   Greg KH <greg@...ah.com>
To:     Vinod Koul <vkoul@...nel.org>
Cc:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Kishon Vijay Abraham I <kishon@...com>,
        Jon Hunter <jonathanh@...dia.com>,
        Sing-Han Chen <singhanc@...dia.com>,
        Wayne Chang <waynec@...dia.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: duplicate patches in the phy-next tree

On Thu, Jan 19, 2023 at 11:42:43AM +0530, Vinod Koul wrote:
> On 19-01-23, 15:31, Stephen Rothwell wrote:
> > Hi all,
> > 
> > The following commits are also in the usb tree as different commits
> > (but the same patches):
> > 
> >   5c7f94f8bad8 ("phy: tegra: xusb: Add Tegra234 support")
> >   e5f9124404d0 ("phy: tegra: xusb: Disable trk clk when not in use")
> > 
> > they are commits
> > 
> >   d8163a32ca95 ("phy: tegra: xusb: Add Tegra234 support")
> >   71d9e899584e ("phy: tegra: xusb: Disable trk clk when not in use")
> 
> Ah, ideally these should go thru phy tree!

Yeah, but they were submitted as a larger set of patches with USB
changes to me, so I took the whole series (it's hard to pick and choose
from a series).

I can revert them from the USB tree, but what harm are they causing now
as duplicates?

thanks,

greg k-h