From: Marcel Ziswiler <marcel.ziswiler@toradex•com>
To: "sfr@canb•auug.org.au" <sfr@canb•auug.org.au>,
"shawnguo@kernel•org" <shawnguo@kernel•org>
Cc: "linux-next@vger•kernel.org" <linux-next@vger•kernel.org>,
Max Krummenacher <max.krummenacher@toradex•com>,
"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the imx-mxs tree
Date: Mon, 24 Oct 2022 07:07:26 +0000 [thread overview]
Message-ID: <e111222f3c3157ad6c81022fa66e6cbc9072f9af.camel@toradex.com> (raw)
In-Reply-To: <20221024153720.5e387e34@canb.auug.org.au>
Hi Stephen
On Mon, 2022-10-24 at 15:37 +1100, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> c9545754e9a7 ("arm64: dts: verdin-imx8mp: fix ctrl_sleep_moci")
>
> Fixes tag
>
> Fixes: 1d8df9c74bff ("arm64: dts: freescale: add initial support for verdin imx8m plus")
Oh shoot, I guess Max referenced the commit from our downstream branch and while I checked the commit to exist
on my end I missed it being a downstream one:
⬢[zim@toolbox linux-toradex-imx.git]$ git branch --contains 1d8df9c74bff5d36d755324be1e695abf9cdeca8
toradex_5.15-2.0.x-imx
> has these problem(s):
>
> - Target SHA1 does not exist
>
> Maybe you meant
>
> Fixes: a39ed23bdf6e ("arm64: dts: freescale: add initial support for verdin imx8m plus")
Yes, Indeed, that must be the correct one:
⬢[zim@toolbox linux-next.git]$ git branch --contains a39ed23bdf6ec7eb0f093b6ef0391e1f3d152f71
v5.19
v6.0
Sorry about that!
@Shawn: Can you fix this up or do I need to re-send anything?
Thanks!
Cheers
Marcel
next prev parent reply other threads:[~2022-10-24 7:07 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 4:37 linux-next: Fixes tag needs some work in the imx-mxs tree Stephen Rothwell
2022-10-24 6:50 ` Francesco Dolcini
2022-10-24 7:07 ` Marcel Ziswiler [this message]
2022-10-29 8:27 ` Shawn Guo
-- strict thread matches above, loose matches on Subject: below --
2025-10-27 20:33 Stephen Rothwell
2025-10-28 7:54 ` Frieder Schrempf
2025-10-28 9:06 ` Shawn Guo
2023-12-06 4:47 Stephen Rothwell
2023-12-06 5:25 ` Shawn Guo
2023-11-27 4:25 Stephen Rothwell
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=e111222f3c3157ad6c81022fa66e6cbc9072f9af.camel@toradex.com \
--to=marcel.ziswiler@toradex$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=max.krummenacher@toradex$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=shawnguo@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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