linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andy Gross <agross@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patch in the usb tree
Date: Wed, 8 Jan 2025 10:23:24 +0100	[thread overview]
Message-ID: <2025010809-glowing-colonize-9cdd@gregkh> (raw)
In-Reply-To: <20250108140352.177285ae@canb.auug.org.au>

On Wed, Jan 08, 2025 at 02:03:52PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> The following commit is also in the qcom tree as a different commit
> (but the same patch):
> 
>   485ff9860801 ("arm64: dts: qcom: x1e80100-qcp: Enable external DP support")
> 
> This is commit
> 
>   5f440a7b003e ("arm64: dts: qcom: x1e80100-qcp: Enable external DP support")
> 
> in the usb tree.

Ah, sorry about that, merging these should be fine, thanks for letting
me know.

greg k-h

  reply	other threads:[~2025-01-08  9:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-08  3:03 linux-next: duplicate patch in the usb tree Stephen Rothwell
2025-01-08  9:23 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-08-16  2:37 Stephen Rothwell
2024-08-16  7:23 ` Greg KH
2023-06-15  5:19 Stephen Rothwell
2023-06-15  6:42 ` Wolfram Sang
2023-06-15  6:48   ` Greg KH
2023-03-28  2:11 Stephen Rothwell
2023-03-28  5:27 ` Greg KH
2023-03-28  6:16   ` Shawn Guo
2023-02-08  1:17 Stephen Rothwell
2023-02-08  7:35 ` Greg KH
2023-01-19  4:26 Stephen Rothwell
2023-01-19 12:05 ` Greg KH
2023-01-19 13:24   ` Thierry Reding
2023-01-20 14:04     ` 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=2025010809-glowing-colonize-9cdd@gregkh \
    --to=greg@kroah.com \
    --cc=agross@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).