On Fri, 21 Mar 2025 at 08:33, Avri Altman <Avri.Altman@xxxxxxxxxxx> 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@xxxxxxx>
> Date: Sun Oct 6 08:11:42 2024 +0300
>
> mmc: core: Add open-ended Ext memory addressing
>
> commit 403a0293f1c230524e0185b31f69c02a6aed12c7
> Author: Avri Altman <avri.altman@xxxxxxx>
> 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
