From: LeeWeiTse <scott6986@gmail.com>
To: Mark Brown <broonie@kernel.org>, Seven Lee <wtli@nuvoton.com>
Cc: alsa-devel@alsa-project.org, SJLIN0@nuvoton.com,
KCHSU0@nuvoton.com, lgirdwood@gmail.com, YHCHuang@nuvoton.com,
CTLIN0@nuvoton.com, dardar923@gmail.com,
supercraig0719@gmail.com
Subject: Re: [PATCH] ASoC: nau8821: Implement DRC controls
Date: Mon, 30 Jan 2023 19:32:00 +0800 [thread overview]
Message-ID: <76e2e7a4-a9c6-1291-9995-beddd13f2e4d@gmail.com> (raw)
In-Reply-To: <Y71eG0VgAkntqH0I@sirena.org.uk>
Mark Brown 寫道:
> On Tue, Jan 10, 2023 at 11:16:22AM +0800, Seven Lee wrote:
>> This patch is support dynamic range compression controls.
>>
>> Signed-off-by: Seven Lee<wtli@nuvoton.com>
> This still isn't applying for me, for example on my for-6.3 branch:
>
> Applying: ASoC: nau8821: Implement DRC controls
> Using index info to reconstruct a base tree...
> error: patch failed: sound/soc/codecs/nau8821.c:322
> error: sound/soc/codecs/nau8821.c: patch does not apply
> error: patch failed: sound/soc/codecs/nau8821.h:350
> error: sound/soc/codecs/nau8821.h: patch does not apply
> error: Did you hand edit your patch?
> It does not apply to blobs recorded in its index.
> Patch failed at 0002 ASoC: nau8821: Implement DRC controls
>
> Are you sure you don't have any other changes in your tree?
Sorry, this is my company mail server setup for network security.
I will send the patch again by my Gmail, thanks.
next prev parent reply other threads:[~2023-01-30 11:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 3:16 [PATCH] ASoC: nau8821: Implement DRC controls Seven Lee
2023-01-10 12:46 ` Mark Brown
2023-01-30 11:32 ` LeeWeiTse [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-17 9:25 Seven Lee
2023-01-31 9:25 Seven Lee
2023-01-10 3:14 Seven Lee
2023-01-09 11:15 Seven Lee
2023-01-09 16:37 ` 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=76e2e7a4-a9c6-1291-9995-beddd13f2e4d@gmail.com \
--to=scott6986@gmail.com \
--cc=CTLIN0@nuvoton.com \
--cc=KCHSU0@nuvoton.com \
--cc=SJLIN0@nuvoton.com \
--cc=YHCHuang@nuvoton.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=dardar923@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=supercraig0719@gmail.com \
--cc=wtli@nuvoton.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