From: Juerg Haefliger <juerg.haefliger@canonical.com>
To: sbinding@opensource.cirrus.com
Cc: linux-firmware@kernel.org
Subject: linux-firmware: Duplicate links
Date: Fri, 2 Feb 2024 15:40:32 +0100 [thread overview]
Message-ID: <20240202154032.52fb9475@gollum> (raw)
[-- Attachment #1: Type: text/plain, Size: 1088 bytes --]
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>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2024-02-02 14:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 14:40 Juerg Haefliger [this message]
2024-02-02 15:17 ` linux-firmware: Duplicate links Stefan Binding
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=20240202154032.52fb9475@gollum \
--to=juerg.haefliger@canonical.com \
--cc=linux-firmware@kernel.org \
--cc=sbinding@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox