From: Mark Brown <broonie@kernel.org>
To: "Paweł Anikiel" <pan@semihalf.com>
Cc: alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, lgirdwood@gmail.com,
perex@perex.cz, tiwai@suse.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, dinguyen@kernel.org,
lars@metafoo.de, nuno.sa@analog.com, upstream@semihalf.com
Subject: Re: [PATCH 0/9] Add Chameleon v3 ASoC audio
Date: Fri, 14 Apr 2023 17:47:02 +0100 [thread overview]
Message-ID: <6d90ad41-bb2d-41a0-8a4a-922b78967a2e@sirena.org.uk> (raw)
In-Reply-To: <20230414140203.707729-1-pan@semihalf.com>
[-- Attachment #1: Type: text/plain, Size: 715 bytes --]
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?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-04-14 16:47 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 14:01 Paweł Anikiel
2023-04-14 14:01 ` [PATCH 1/9] ASoC: Add Chameleon v3 audio Paweł Anikiel
2023-04-14 16:57 ` Krzysztof Kozlowski
2023-04-14 17:19 ` Mark Brown
2023-04-25 15:59 ` Paweł Anikiel
2023-04-25 16:27 ` Mark Brown
2023-04-14 14:01 ` [PATCH 2/9] dt-bindings: ASoC: Add chv3-i2s Paweł Anikiel
2023-04-14 17:00 ` Krzysztof Kozlowski
2023-04-25 16:01 ` Paweł Anikiel
2023-04-26 13:15 ` Krzysztof Kozlowski
2023-04-14 14:01 ` [PATCH 3/9] dt-bindings: ASoC: Add chv3-audio Paweł Anikiel
2023-04-14 18:37 ` Rob Herring
2023-04-17 20:41 ` Rob Herring
2023-04-25 16:01 ` Paweł Anikiel
2023-04-14 14:01 ` [PATCH 4/9] dt-bindings: ASoC: Add it68051 Paweł Anikiel
2023-04-14 17:01 ` Krzysztof Kozlowski
2023-04-14 18:37 ` Rob Herring
2023-04-14 14:01 ` [PATCH 5/9] ASoC: ssm2602: Add workaround for playback with external MCLK Paweł Anikiel
2023-04-14 17:35 ` Mark Brown
2023-04-25 16:02 ` Paweł Anikiel
2023-04-25 16:42 ` Mark Brown
2023-04-14 14:02 ` [PATCH 6/9] ASoC: ssm2602: Add support for CLKDIV2 Paweł Anikiel
2023-04-14 14:02 ` [PATCH 7/9] ASoC: ssm2602: Add mute gpio Paweł Anikiel
2023-04-14 17:47 ` Mark Brown
2023-04-14 14:02 ` [PATCH 8/9] dt-bindings: ASoC: Add mute-gpio to ssm2602 Paweł Anikiel
2023-04-14 14:02 ` [PATCH 9/9] ARM: dts: chameleonv3: Add ssm2603 mute gpio Paweł Anikiel
2023-04-14 16:47 ` Mark Brown [this message]
2023-04-25 15:58 ` [PATCH 0/9] Add Chameleon v3 ASoC audio Paweł Anikiel
2023-04-25 17:06 ` Mark Brown
2023-04-17 19:28 ` (subset) " Mark Brown
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=6d90ad41-bb2d-41a0-8a4a-922b78967a2e@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=pan@semihalf.com \
--cc=perex@perex.cz \
--cc=robh+dt@kernel.org \
--cc=tiwai@suse.com \
--cc=upstream@semihalf.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®