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: Windows password security audit tool. GUI, reports in PDF.

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

Date:   Sat, 29 Oct 2022 16:27:38 +0800
From:   Shawn Guo <shawnguo@...nel.org>
To:     Marcel Ziswiler <marcel.ziswiler@...adex.com>
Cc:     "sfr@...b.auug.org.au" <sfr@...b.auug.org.au>,
        "linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
        Max Krummenacher <max.krummenacher@...adex.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the imx-mxs tree

On Mon, Oct 24, 2022 at 07:07:26AM +0000, Marcel Ziswiler wrote:
> 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@...lbox 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@...lbox 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?

Fixed.

Shawn