mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, lgirdwood@gmail.com,
	"Paweł Anikiel" <pan@semihalf.com>
Cc: 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,
	amstan@chromium.org
Subject: Re: (subset) [PATCH v2 0/7] Add Chameleon v3 ASoC audio
Date: Fri, 19 May 2023 07:29:08 +0900	[thread overview]
Message-ID: <168444894844.494451.621381852845902140.b4-ty@kernel.org> (raw)
In-Reply-To: <20230508113037.137627-1-pan@semihalf.com>

On Mon, 08 May 2023 13:30:30 +0200, Paweł Anikiel wrote:
> The Google Chameleon v3 is a device made for testing audio and video
> paths of other devices. This patchset adds support for ASoC audio on
> this device. It has two audio sources: HDMI audio from the it68051 chip
> (RX only), and analog audio from the ssm2603 chip (RX and TX).
> 
> The patchset adds the ASoC platform and codec drivers, as well as some
> changes to the existing ssm2602 codec driver.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/7] ASoC: Add Google Chameleon v3 i2s driver
      commit: 702648721db590b3425c31ade294000e18808345
[2/7] ASoC: Add Google Chameleon v3 codec driver
      commit: 61ed303496eb7e18491ee617dec2403f75d5168c
[3/7] ASoC: dt-bindings: Add Google Chameleon v3 i2s device
      commit: 6f2c1e7c2546f9eab0031843fb7346e49ba69102
[4/7] ASoC: dt-bindings: Add Google Chameleon v3 audio codec
      commit: 580bac2a2c6f7d106be6d0ee0f0f310be49368b3

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark


      parent reply	other threads:[~2023-05-18 22:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-08 11:30 Paweł Anikiel
2023-05-08 11:30 ` [PATCH v2 1/7] ASoC: Add Google Chameleon v3 i2s driver Paweł Anikiel
2023-05-08 11:30 ` [PATCH v2 2/7] ASoC: Add Google Chameleon v3 codec driver Paweł Anikiel
2023-05-08 11:30 ` [PATCH v2 3/7] ASoC: dt-bindings: Add Google Chameleon v3 i2s device Paweł Anikiel
2023-05-08 12:27   ` Rob Herring
2023-05-09  6:14     ` Krzysztof Kozlowski
2023-05-09  6:15   ` Krzysztof Kozlowski
2023-05-08 11:30 ` [PATCH v2 4/7] ASoC: dt-bindings: Add Google Chameleon v3 audio codec Paweł Anikiel
2023-05-08 12:27   ` Rob Herring
2023-05-09  6:18   ` Krzysztof Kozlowski
2023-05-09  9:54     ` Mark Brown
2023-05-09 10:39       ` Paweł Anikiel
2023-05-08 11:30 ` [PATCH v2 5/7] ARM: dts: chameleonv3: Add mute gpio hog Paweł Anikiel
2023-05-08 11:30 ` [PATCH v2 6/7] ARM: dts: chameleonv3: Add Chameleon v3 audio Paweł Anikiel
2023-05-08 11:30 ` [PATCH v2 7/7] ASoC: ssm2602: Add workaround for playback distortions Paweł Anikiel
2023-05-12  4:19 ` (subset) [PATCH v2 0/7] Add Chameleon v3 ASoC audio Mark Brown
2023-05-18 22:29 ` Mark Brown [this message]

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=168444894844.494451.621381852845902140.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=amstan@chromium.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®