public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Kishon Vijay Abraham I <kishon@ti.com>, Greg KH <greg@kroah.com>,
	Jon Hunter <jonathanh@nvidia.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	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 11:42:43 +0530	[thread overview]
Message-ID: <Y8jfW2TTnHd3J7R1@matsya> (raw)
In-Reply-To: <20230119153145.598885cf@canb.auug.org.au>

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!

> 
> in the usb tree.
> 
> -- 
> Cheers,
> Stephen Rothwell



-- 
~Vinod

  reply	other threads:[~2023-01-19  6:13 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 [this message]
2023-01-19  6:54   ` Greg KH
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=Y8jfW2TTnHd3J7R1@matsya \
    --to=vkoul@kernel.org \
    --cc=greg@kroah.com \
    --cc=gregkh@linuxfoundation.org \
    --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=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