linux-kernel - Re: linux-next: Fixes tag needs some work in the imx-mxs tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1c67886b-730e-4a6d-a846-d5e932b452bc@kontron.de>
Date: Tue, 28 Oct 2025 08:54:17 +0100
From: Frieder Schrempf <frieder.schrempf@...tron.de>
To: Stephen Rothwell <sfr@...b.auug.org.au>, Shawn Guo <shawnguo@...nel.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
 Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the imx-mxs tree

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?