From: Daniel Abrecht <linux-sound@nodmarc.danielabrecht.ch>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ASoC: soc-core.c: Add "Unknown" and "Unknown Product" to dmi_blacklist
Date: Mon, 22 Jan 2024 18:53:42 +0100 [thread overview]
Message-ID: <83d18087378efb6b6f1133573719ca57@nodmarc.danielabrecht.ch> (raw)
In-Reply-To: <e90440a5-587b-48b2-a61f-0800aa8200d5@sirena.org.uk>
Am 2024-01-22 16:30, schrieb Mark Brown:
> On Wed, Jan 17, 2024 at 02:44:43PM +0100, Daniel Abrecht wrote:
>> In U-Boot, the default for DMI vendor / product if not set is "Unknown" and
>> "Unknown Product".
>> See https://source.denx.de/u-boot/u-boot/-/blob/v2023.10/lib/smbios.c?ref_type=tags#L272
>
> This is still corrupted according to git am unfortunately. I can't
> immediately spot the issue.
The v3 I sent applies just fine with "git am" as far as I can tell. I just tested it again with the mail form the list.
I think the v3 patch is fine, but this time, the v3 message ended up with the same message ID as the v2 message.
Because of this, some mail clients may get confused, and the threading in mail clients is going to be broken.
prev parent reply other threads:[~2024-01-22 17:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 13:44 Daniel Abrecht
2024-01-22 0:05 ` Mark Brown
2024-01-22 9:36 ` [PATCH v3] " Daniel Abrecht
2024-01-22 9:46 ` Daniel Abrecht
2024-01-22 15:30 ` [PATCH v2] " Mark Brown
2024-01-22 17:53 ` Daniel Abrecht [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=83d18087378efb6b6f1133573719ca57@nodmarc.danielabrecht.ch \
--to=linux-sound@nodmarc.danielabrecht.ch \
--cc=broonie@kernel.org \
--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®