From: Mark Brown <broonie@kernel.org>
To: Zhang Yi <zhangyi@everest-semi.com>
Cc: robh@kernel.org, tiwai@suse.com, devicetree@vger.kernel.org,
conor+dt@kernel.org, lgirdwood@gmail.com,
linux-kernel@vger.kernel.org, linux-sound@vger.kernel.org,
perex@perex.cz, krzk+dt@kernel.org,
amadeuszx.slawinski@linux.intel.com, krzk@kernel.org
Subject: Re: [RESEND v7 0/2] ASoC: codecs: add support for ES8389
Date: Wed, 14 May 2025 11:12:14 +0200 [thread overview]
Message-ID: <aCRebl_L2db3ZJsj@finisterre.sirena.org.uk> (raw)
In-Reply-To: <20250514090257.34585-1-zhangyi@everest-semi.com>
[-- Attachment #1: Type: text/plain, Size: 1106 bytes --]
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-05-14 9:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 9:02 [RESEND v7 0/2] ASoC: codecs: add support for ES8389 Zhang Yi
2025-05-14 9:12 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-14 9:42 Zhang Yi
2025-05-14 3:33 Zhang Yi
2025-05-14 7:40 ` Mark Brown
2025-05-15 12:08 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aCRebl_L2db3ZJsj@finisterre.sirena.org.uk \
--to=broonie@kernel.org \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=robh@kernel.org \
--cc=tiwai@suse.com \
--cc=zhangyi@everest-semi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox