[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <9c459c3f-7a7b-42d6-8a4c-66ade94e1029@infradead.org>
Date: Wed, 17 Sep 2025 10:58:17 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: cryolitia@...ontech.com, Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>, Jonathan Corbet <corbet@....net>,
Luis Chamberlain <mcgrof@...nel.org>, Petr Pavlu <petr.pavlu@...e.com>,
Daniel Gomez <da.gomez@...nel.org>, Sami Tolvanen <samitolvanen@...gle.com>
Cc: linux-sound@...r.kernel.org, linux-usb@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
Mingcong Bai <jeffbai@...c.io>, Kexy Biscuit <kexybiscuit@...c.io>,
Nie Cheng <niecheng1@...ontech.com>, Zhan Jun <zhanjun@...ontech.com>,
Feng Yuan <fengyuan@...ontech.com>, qaqland <anguoli@...ontech.com>,
kernel@...ontech.com, linux-modules@...r.kernel.org
Subject: Re: [PATCH v3 4/4] ALSA: doc: add docs about
device_device_quirk_flags in snd-usb-audio
On 9/17/25 5:46 AM, Cryolitia PukNgae via B4 Relay wrote:
> @@ -2344,8 +2386,8 @@ report it to the upstream.
> NB: ``quirk_alias`` option is provided only for testing / development.
> If you want to have a proper support, contact to upstream for
> adding the matching quirk in the driver code statically.
> -Ditto for ``quirk_flags``. If a device is known to require specific
> -workarounds, please report to the upstream.
> +Ditto for ``quirk_flags``. If a device
> +is known to require specific workarounds, please report to the upstream.
What is the purpose of this change?
--
~Randy
Powered by blists - more mailing lists