From: Christian Hewitt <christianshewitt@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Jonas Karlman <jonas@kwiboo.se>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
Matthias Reichl <hias@horus.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Jani Nikula <jani.nikula@intel.com>
Subject: Re: [RESEND v2] ASoC: hdmi-codec: reorder channel allocation list
Date: Fri, 15 Nov 2024 08:45:48 +0400 [thread overview]
Message-ID: <A5A3A740-7FB3-42BC-A723-2648ECE959C6@gmail.com> (raw)
In-Reply-To: <ZzXiJIyf8Iyb7f50@finisterre.sirena.org.uk>
> On 14 Nov 2024, at 3:42 pm, Mark Brown <broonie@kernel.org> wrote:
>
> On Tue, Nov 12, 2024 at 09:07:00AM +0400, Christian Hewitt wrote:
>> From: Jonas Karlman <jonas@kwiboo.se>
>>
>> The ordering in hdmi_codec_get_ch_alloc_table_idx() results in
>> wrong channel allocation for a number of cases, e.g. when ELD
>> reports FL|FR|LFE|FC|RL|RR or FL|FR|LFE|FC|RL|RR|RC|RLC|RRC:
>
> This doesn't apply against current code, please check and resend.
>
> Applying: ASoC: hdmi-codec: reorder channel allocation list
> error: corrupt patch at line 6
> error: could not build fake ancestor
> Patch failed at 0004 ASoC: hdmi-codec: reorder channel allocation list
Looks like mail client ‘resend’ broke the patch, apologies. I’ve sent
a v3 to the list to ensure it’s distinct and formatted correctly.
CH.
prev parent reply other threads:[~2024-11-15 4:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 5:07 Christian Hewitt
2024-11-14 11:42 ` Mark Brown
2024-11-15 4:45 ` Christian Hewitt [this message]
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=A5A3A740-7FB3-42BC-A723-2648ECE959C6@gmail.com \
--to=christianshewitt@gmail.com \
--cc=broonie@kernel.org \
--cc=hias@horus.com \
--cc=jani.nikula@intel.com \
--cc=jbrunet@baylibre.com \
--cc=jonas@kwiboo.se \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.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
all inboxes | Powered by JetHome®