mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: "Shenghao Ding" <shenghao-ding@ti.com>,
	"Kevin Lu" <kevin-lu@ti.com>, "Baojun Xu" <baojun.xu@ti.com>,
	"Liam Girdwood" <lgirdwood@gmail.com>,
	"Jaroslav Kysela" <perex@perex.cz>,
	"Takashi Iwai" <tiwai@suse.com>, "Dan Murphy" <dmurphy@ti.com>,
	"Hector Martin" <marcan@marcan.st>,
	"Martin Povišer" <povik+lin@cutebit.org>,
	broonie@kernel.org
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
	 devicetree@vger.kernel.org
Subject: Re: [PATCH 0/4] ASoC: tas2764: Random patches from the Asahi Linux tree
Date: Mon, 17 Feb 2025 14:32:27 +0000	[thread overview]
Message-ID: <173980274756.49890.13014040253628029521.b4-ty@kernel.org> (raw)
In-Reply-To: <20250208-asoc-tas2764-v1-0-dbab892a69b5@kernel.org>

On Sat, 08 Feb 2025 01:03:23 +0000, broonie@kernel.org wrote:
> This is a random subset of the patches for the tas2764 driver that I
> found in the Asahi Linux tree which seemed to be clear fixes and
> improvements which apply easily to mainline without much effort, there's
> a bunch more work on the driver that should also be applicable.
> 
> I've only build tested this.
> 
> [...]

Applied to

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

Thanks!

[1/4] ASoC: tas2764: Power up/down amp on mute ops
      commit: 1c3b5f37409682184669457a5bdf761268eafbe5
[2/4] ASoC: tas2764: Wait for ramp-down after shutdown
      commit: 08a66f55f7246d477b19620a953476dfc02beefc
[3/4] ASoC: tas2764: Mark SW_RESET as volatile
      commit: f37f1748564ac51d32f7588bd7bfc99913ccab8e
[4/4] ASoC: tas2764: Add reg defaults for TAS2764_INT_CLK_CFG
      commit: d64c4c3d1c578f98d70db1c5e2535b47adce9d07

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:[~2025-02-17 14:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-08  1:03 broonie
2025-02-08  1:03 ` [PATCH 1/4] ASoC: tas2764: Power up/down amp on mute ops broonie
2025-02-08  1:03 ` [PATCH 2/4] ASoC: tas2764: Wait for ramp-down after shutdown broonie
2025-02-08  1:03 ` [PATCH 3/4] ASoC: tas2764: Mark SW_RESET as volatile broonie
2025-02-08  1:03 ` [PATCH 4/4] ASoC: tas2764: Add reg defaults for TAS2764_INT_CLK_CFG broonie
2025-02-17 14:32 ` 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=173980274756.49890.13014040253628029521.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=baojun.xu@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmurphy@ti.com \
    --cc=kevin-lu@ti.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=marcan@marcan.st \
    --cc=perex@perex.cz \
    --cc=povik+lin@cutebit.org \
    --cc=shenghao-ding@ti.com \
    --cc=tiwai@suse.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®