linux-kernel - Re: linux-next: Fixes tag needs some work in the mmc 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] [day] [month] [year] [list]

Message-ID: <CAPDyKFoMZbr+CDf0LeyQ_WxpTW=b_gGp5q8y-PPo+0MBNnyJJQ@mail.gmail.com>
Date: Fri, 21 Mar 2025 09:52:57 +0100
From: Ulf Hansson <ulf.hansson@...aro.org>
To: Avri Altman <Avri.Altman@...disk.com>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>, 
	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 mmc tree

On Fri, 21 Mar 2025 at 08:33, Avri Altman <Avri.Altman@...disk.com> wrote:
>
> > > Hi all,
> > >
> > > In commit
> > >
> > >   79055e47336e ("mmc: core: Remove redundant null check")
> > >
> > > Fixes tag
> > >
> > >   Fixes: 737d220bb2be ("mmc: core: Add open-ended Ext memory
> > > addressing")
> > >
> > > has these problem(s):
> > >
> > >   - Target SHA1 does not exist
> > I was using Ulf's for/next branch, as I always do, and their the sha1 is
> > 737d220bb2be.
> > Should I be using different tree/branch ?
> I apologize.  Looks like 403a0293f1c2 does exist and presumably point to the same commit (impossible):
>
> commit 737d220bb2bef9efd43267c757faff003533b631
> Author: Avri Altman <avri.altman@....com>
> Date:   Sun Oct 6 08:11:42 2024 +0300
>
>     mmc: core: Add open-ended Ext memory addressing
>
> commit 403a0293f1c230524e0185b31f69c02a6aed12c7
> Author: Avri Altman <avri.altman@....com>
> Date:   Sun Oct 6 08:11:42 2024 +0300
>
>     mmc: core: Add open-ended Ext memory addressing
>
> I guess something in the metadata is different.

Sometimes I am re-basing my tree, so I am guessing the sha is from an
old tree/branch.

Anway I have moved to use 403a0293f1c2 as that should be the correct one.

[...]

Kind regards
Uffe