From: Shawn Guo <shawnguo@kernel.org>
To: Greg KH <greg@kroah.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Peng Fan <peng.fan@nxp.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: Tue, 28 Mar 2023 14:16:36 +0800 [thread overview]
Message-ID: <20230328061636.GQ3364759@dragon> (raw)
In-Reply-To: <ZCJ62nDO3PocFPeP@kroah.com>
On Tue, Mar 28, 2023 at 07:27:54AM +0200, Greg KH wrote:
> On Tue, Mar 28, 2023 at 01:11:10PM +1100, Stephen Rothwell wrote:
> > Hi all,
> >
> > The following commit is also in the imx-mxs tree as a different commit
> > (but the same patch):
> >
> > fcd3f50845be ("arm64: dts: imx8mq: drop usb3-resume-missing-cas from usb")
> >
> > This is commit
> >
> > 989e2ee399cd ("arm64: dts: imx8mq: drop usb3-resume-missing-cas from usb")
> >
> > in the imx-mxs tree.
>
> Thanks, I can revert this in the imx-mxs tree, but it should be fine
> when Linus merges so I doubt that is needed.
My branch is not stable anyway, so I'm dropping the copy here.
Shawn
next prev parent reply other threads:[~2023-03-28 6:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 2:11 linux-next: duplicate patch in the usb tree Stephen Rothwell
2023-03-28 5:27 ` Greg KH
2023-03-28 6:16 ` Shawn Guo [this message]
-- 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-06-15 5:19 Stephen Rothwell
2023-06-15 6:42 ` Wolfram Sang
2023-06-15 6:48 ` Greg KH
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=20230328061636.GQ3364759@dragon \
--to=shawnguo@kernel.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=peng.fan@nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.