[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yj12vorW0FW8S6Sm@infradead.org>
Date: Fri, 25 Mar 2022 01:01:02 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Oh Eomji <eomji.oh@...sung.com>
Cc: Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
open list <linux-kernel@...r.kernel.org>,
alsa-devel@...a-project.org, Leon Romanovsky <leon@...nel.org>,
Pavel Skripkin <paskripkin@...il.com>,
JaeHun Jung <jh0801.jung@...sung.com>
Subject: Re: [PATCH v1 1/3] sound: usb: Add vendor's hooking interface
Independ of the actual usefulness of thi: vendor is a reallly bogus
naming choice for device specific hooks. No one cares what vendor
produces a given device, it is all about the interface of it. One
vendor might have different interfaces over time, from different
divisons or thrugh acquisitions, and multiple vendors can agree to
a single interface through open standards or IP licensing.
Powered by blists - more mailing lists