All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Tzung-Bi Shih <tzungbi@google.com>
Cc: alsa-devel@alsa-project.org, trevor.wu@mediatek.com,
	jiaxin.yu@mediatek.com
Subject: Re: [PATCH 0/4] ASoC: mediatek: fix device_node leak
Date: Fri, 24 Dec 2021 16:17:32 +0000	[thread overview]
Message-ID: <164036265260.3720027.15119723749705753132.b4-ty@kernel.org> (raw)
In-Reply-To: <20211224064719.2031210-1-tzungbi@google.com>

On Fri, 24 Dec 2021 14:47:15 +0800, Tzung-Bi Shih wrote:
> The series is a follow up series.
> 
> The 1st and 2nd patch follow [1] to fix the device_node leak.
> 
> The 3rd patch follows [2] to reduce the log verbosity.
> 
> The 4th patch cleans the device_node related code on MT8195.
> In order to align to previous platforms.
> 
> [...]

Applied to

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

Thanks!

[1/4] ASoC: mediatek: mt8173: fix device_node leak
      commit: 493433785df0075afc0c106ab65f10a605d0b35d
[2/4] ASoC: mediatek: mt8183: fix device_node leak
      commit: cb006006fe6221f092fadaffd3f219288304c9ad
[3/4] ASoC: mediatek: mt8173: reduce log verbosity in probe()
      commit: db3f5abe68ea5ea39d84e6af4f0f2ce5d5e2daf4
[4/4] ASoC: mediatek: mt8195: release device_node after snd_soc_register_card
      commit: 082482a5022780d42180a394fe6843e71fe963d8

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:[~2021-12-24 16:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-24  6:47 [PATCH 0/4] ASoC: mediatek: fix device_node leak Tzung-Bi Shih
2021-12-24  6:47 ` [PATCH 1/4] ASoC: mediatek: mt8173: " Tzung-Bi Shih
2021-12-24  6:47 ` [PATCH 2/4] ASoC: mediatek: mt8183: " Tzung-Bi Shih
2021-12-24  6:47 ` [PATCH 3/4] ASoC: mediatek: mt8173: reduce log verbosity in probe() Tzung-Bi Shih
2021-12-24  6:47 ` [PATCH 4/4] ASoC: mediatek: mt8195: release device_node after snd_soc_register_card Tzung-Bi Shih
2021-12-24 16:17 ` 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=164036265260.3720027.15119723749705753132.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=jiaxin.yu@mediatek.com \
    --cc=trevor.wu@mediatek.com \
    --cc=tzungbi@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.