From: Wolfram Sang <wsa@the-dreams.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Greg KH <greg@kroah.com>,
Mario Limonciello <mario.limonciello@amd.com>,
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: Thu, 15 Jun 2023 08:42:26 +0200 [thread overview]
Message-ID: <ZIqy0mLPipq2p/N8@ninjato> (raw)
In-Reply-To: <20230615151958.46746fe8@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 539 bytes --]
Hi,
> The following commit is also in the i2c tree as a different commit
> (but the same patch):
thank you for the pointer!
>
> 7b7efc925042 ("usb: typec: ucsi: Mark dGPUs as DEVICE scope")
>
> This is commit
>
> a7fbfd44c020 ("usb: typec: ucsi: Mark dGPUs as DEVICE scope")
>
> in the ic2 tree.
Oh, sorry, I didn't get a mail that it was already applied to the
usb-tree. Maybe I accidently erased it. What is the procedure now? I
guess I revert the version in the i2c tree?
All the best,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-06-15 7:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 5:19 linux-next: duplicate patch in the usb tree Stephen Rothwell
2023-06-15 6:42 ` Wolfram Sang [this message]
2023-06-15 6:48 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2025-01-08 3:03 Stephen Rothwell
2025-01-08 9:23 ` Greg KH
2024-08-16 2:37 Stephen Rothwell
2024-08-16 7:23 ` 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=ZIqy0mLPipq2p/N8@ninjato \
--to=wsa@the-dreams.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--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).