From: Greg KH <greg@kroah.com>
To: Vinod Koul <vkoul@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Kishon Vijay Abraham I <kishon@ti.com>,
Jon Hunter <jonathanh@nvidia.com>,
Sing-Han Chen <singhanc@nvidia.com>,
Wayne Chang <waynec@nvidia.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patches in the phy-next tree
Date: Thu, 19 Jan 2023 07:54:15 +0100 [thread overview]
Message-ID: <Y8jpFw5mfvyRLX/C@kroah.com> (raw)
In-Reply-To: <Y8jfW2TTnHd3J7R1@matsya>
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
next prev parent reply other threads:[~2023-01-19 6:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 4:31 linux-next: duplicate patches in the phy-next tree Stephen Rothwell
2023-01-19 6:12 ` Vinod Koul
2023-01-19 6:54 ` Greg KH [this message]
2023-01-19 13:45 ` Thierry Reding
2023-01-19 17:33 ` Theodore Ts'o
2023-01-20 14:02 ` Greg KH
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=Y8jpFw5mfvyRLX/C@kroah.com \
--to=greg@kroah.com \
--cc=jonathanh@nvidia.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=singhanc@nvidia.com \
--cc=vkoul@kernel.org \
--cc=waynec@nvidia.com \
/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