lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Mon, 22 Jan 2024 18:53:42 +0100
From: Daniel Abrecht <linux-sound@...marc.danielabrecht.ch>
To: Mark Brown <broonie@...nel.org>
Cc: Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>,
 Takashi Iwai <tiwai@...e.com>, linux-sound@...r.kernel.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] ASoC: soc-core.c: Add "Unknown" and "Unknown Product"
 to dmi_blacklist

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.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ