[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6d90ad41-bb2d-41a0-8a4a-922b78967a2e@sirena.org.uk>
Date: Fri, 14 Apr 2023 17:47:02 +0100
From: Mark Brown <broonie@...nel.org>
To: Paweł Anikiel <pan@...ihalf.com>
Cc: alsa-devel@...a-project.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, lgirdwood@...il.com, perex@...ex.cz,
tiwai@...e.com, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, dinguyen@...nel.org,
lars@...afoo.de, nuno.sa@...log.com, upstream@...ihalf.com
Subject: Re: [PATCH 0/9] Add Chameleon v3 ASoC audio
On Fri, Apr 14, 2023 at 04:01:54PM +0200, Paweł Anikiel wrote:
> sound/soc/Makefile | 1 +
> sound/soc/chameleonv3/Kconfig | 7 +
> sound/soc/chameleonv3/Makefile | 2 +
> sound/soc/chameleonv3/chv3-audio.c | 111 ++++++
> sound/soc/chameleonv3/chv3-i2s.c | 347 ++++++++++++++++++
> sound/soc/chameleonv3/chv3-it68051.c | 41 +++
Please at least make a directory for Google as a vendor, we don't want
people adding directories for each individual product. That said
generally we add machine drivers in the directory for the relevant SoC
family, is there any reason that pattern isn't followed here?
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists