RE: [RESEND v7 0/2] ASoC: codecs: add support for ES8389

Zhang Yi posted 2 patches 9 months ago
Only 0 patches received!
There is a newer version of this series
RE: [RESEND v7 0/2] ASoC: codecs: add support for ES8389
Posted by Zhang Yi 9 months ago
> This doesn't apply:
> 
> Applying: ASoC: codecs: add support for ES8389
> error: sha1 information is lacking or useless (sound/soc/codecs/Kconfig).
> error: could not build fake ancestor
> Patch failed at 0001 ASoC: codecs: add support for ES8389
> hint: Use 'git am --show-current-patch=diff' to see the failed patch
> When you have resolved this problem, run "git am --continue".
> If you prefer to skip this patch, run "git am --skip" instead.
> To restore the original branch and stop patching, run "git am --abort".
> broonie@finisterre:~/git/apply$ git am --abort

I'm confused as to why this happened.
I made the patch based on the following branch
https://web.git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/?h=next-20250513
Re: [RESEND v7 0/2] ASoC: codecs: add support for ES8389
Posted by Mark Brown 9 months ago
On Wed, May 14, 2025 at 05:02:57PM +0800, Zhang Yi wrote:

> > Applying: ASoC: codecs: add support for ES8389
> > error: sha1 information is lacking or useless (sound/soc/codecs/Kconfig).
> > error: could not build fake ancestor
> > Patch failed at 0001 ASoC: codecs: add support for ES8389

> I'm confused as to why this happened.
> I made the patch based on the following branch
> https://web.git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/?h=next-20250513

That's not my tree, that's linux-next.  MAINTAINERS shows:

SOUND - SOC LAYER / DYNAMIC AUDIO POWER MANAGEMENT (ASoC)
M:      Liam Girdwood <lgirdwood@gmail.com>
M:      Mark Brown <broonie@kernel.org>
L:      linux-sound@vger.kernel.org
S:      Supported
W:      http://alsa-project.org/main/index.php/ASoC
T:      git git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git

and note that above git is saying it's not got a useful SHA1 in your
patch so either there's a formatting issue or it's not quite -next (the
repo I apply to has -next so would see -next commits).  For things
targetting 6.16 you want for-6.16.