From: Stefan Binding <sbinding@opensource.cirrus.com>
To: 'Juerg Haefliger' <juerg.haefliger@canonical.com>
Cc: <linux-firmware@kernel.org>, <patches@opensource.cirrus.com>
Subject: RE: linux-firmware: Duplicate links
Date: Fri, 2 Feb 2024 15:17:52 +0000 [thread overview]
Message-ID: <002401da55ea$fdc930a0$f95b91e0$@opensource.cirrus.com> (raw)
In-Reply-To: <20240202154032.52fb9475@gollum>
Hi,
Apologies for this.
I currently have a fix for this locally, that I'm planning to send
upstream shortly.
Thanks,
Stefan
> -----Original Message-----
> From: Juerg Haefliger <juerg.haefliger@canonical.com>
> Sent: Friday, February 2, 2024 2:41 PM
> To: sbinding@opensource.cirrus.com
> Cc: linux-firmware@kernel.org
> Subject: linux-firmware: Duplicate links
>
> Stefan,
>
> Your commit [1] introduced duplicate symlinks in WHENCE pointing to
> different
> binaries:
>
> Link: cirrus/cs35l41-dsp1-spk-prot-103c8ca7.wmfw ->
> cs35l41/v6.83.0/halo_cspl_RAM_revB2_29.85.0.wmfw
> Link: cirrus/cs35l41-dsp1-spk-cali-103c8ca7.wmfw ->
> cs35l41/v6.83.0/halo_cspl_RAM_revB2_29.85.0.wmfw
>
> Link: cirrus/cs35l41-dsp1-spk-prot-103c8ca7.wmfw ->
cs35l41-dsp1-spk-
> prot-103c8ca4.bin
> Link: cirrus/cs35l41-dsp1-spk-cali-103c8ca7.wmfw ->
cs35l41-dsp1-spk-
> cali-103c8ca4.bin
>
> Link: cirrus/cs35l41-dsp1-spk-prot-103c8ca7.wmfw ->
> cs35l41/v6.83.0/halo_cspl_RAM_revB2_29.85.0.wmfw
> Link: cirrus/cs35l41-dsp1-spk-cali-103c8ca7.wmfw ->
> cs35l41/v6.83.0/halo_cspl_RAM_revB2_29.85.0.wmfw
>
> Which two are the correct ones?
>
> ...Juerg
>
>
> [1]
> commit 4f498d09a4a6a905f231a52f33886f8a5d22d5de
> Author: Stefan Binding <sbinding@opensource.cirrus.com>
> Date: Fri Oct 20 14:58:26 2023 +0100
>
> linux-firmware: Add firmware for Cirrus CS35L41 on HP G11
Laptops
>
> Support for 3 laptops using CS35L41.
>
> Signed-off-by: Stefan Binding <sbinding@opensource.cirrus.com>
prev parent reply other threads:[~2024-02-02 15:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 14:40 linux-firmware: Duplicate links Juerg Haefliger
2024-02-02 15:17 ` Stefan Binding [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='002401da55ea$fdc930a0$f95b91e0$@opensource.cirrus.com' \
--to=sbinding@opensource.cirrus.com \
--cc=juerg.haefliger@canonical.com \
--cc=linux-firmware@kernel.org \
--cc=patches@opensource.cirrus.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.