From: Shawn Guo <shawnguo2@yeah.net>
To: Frieder Schrempf <frieder.schrempf@kontron.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Shawn Guo <shawnguo@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the imx-mxs tree
Date: Tue, 28 Oct 2025 17:06:01 +0800 [thread overview]
Message-ID: <aQCHeQCHMydd1a--@dragon> (raw)
In-Reply-To: <1c67886b-730e-4a6d-a846-d5e932b452bc@kontron.de>
On Tue, Oct 28, 2025 at 08:54:17AM +0100, Frieder Schrempf wrote:
> Am 27.10.25 um 21:33 schrieb Stephen Rothwell:
> > Hi all,
> >
> > In commit
> >
> > 9bab9019faa5 ("arm64: dts: imx8mp-kontron: Fix USB OTG role switching")
> >
> > Fixes tag
> >
> > Fixes: 827c007db5f2 ("arm64: dts: Add support for Kontron OSM-S i.MX8MP SoM and BL carrier board")
> >
> > has these problem(s):
> >
> > Maybe you meant
> >
> > Fixes: 946ab10e3f40 ("arm64: dts: Add support for Kontron OSM-S i.MX8MP SoM and BL carrier board")
> >
>
> Thanks for the notice. It seems like I accidentally referenced a commit
> from our downstream tree instead of mainline. Sorry for that.
>
> 946ab10e3f40 is the correct reference. Can this be fixed somehow?
I fixed it up.
Shawn
next prev parent reply other threads:[~2025-10-28 9:06 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 20:33 linux-next: Fixes tag needs some work in the imx-mxs tree Stephen Rothwell
2025-10-28 7:54 ` Frieder Schrempf
2025-10-28 9:06 ` Shawn Guo [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-06 4:47 Stephen Rothwell
2023-12-06 5:25 ` Shawn Guo
2023-11-27 4:25 Stephen Rothwell
2022-10-24 4:37 Stephen Rothwell
2022-10-24 6:50 ` Francesco Dolcini
2022-10-24 7:07 ` Marcel Ziswiler
2022-10-29 8:27 ` Shawn Guo
2022-09-13 10:15 Stephen Rothwell
2022-09-13 17:08 ` Tim Harvey
2022-09-14 3:48 ` Shawn Guo
2022-09-14 15:11 ` Tim Harvey
2022-09-05 21:37 Stephen Rothwell
2022-09-06 7:22 ` Marcel Ziswiler
2022-09-06 7:49 ` Shawn Guo
2022-06-13 21:41 Stephen Rothwell
2022-04-18 20:50 Stephen Rothwell
2022-04-19 8:15 ` Max Krummenacher
2022-01-29 23:18 Stephen Rothwell
2021-07-14 22:04 Stephen Rothwell
2021-07-15 11:03 ` Shawn Guo
2020-11-01 21:24 Stephen Rothwell
2020-11-02 0:02 ` Shawn Guo
2020-11-02 8:47 ` Oleksij Rempel
2019-06-06 21:46 Stephen Rothwell
2019-06-07 0:24 ` Shawn Guo
2019-06-11 8:36 ` Peng Fan
2019-06-12 10:51 ` Shawn Guo
2019-06-12 12:15 ` Peng Fan
2019-01-16 20:54 Stephen Rothwell
2019-01-17 0:36 ` Shawn Guo
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=aQCHeQCHMydd1a--@dragon \
--to=shawnguo2@yeah.net \
--cc=frieder.schrempf@kontron.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=shawnguo@kernel.org \
/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.