mirror of https://lore.kernel.org/linux-amlogic/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: tiwai@suse.com, narmstrong@baylibre.com, khilman@baylibre.com,
	perex@perex.cz, jbrunet@baylibre.com, lgirdwood@gmail.com,
	hkallweit1@gmail.com, martin.blumenstingl@googlemail.com
Cc: linux-amlogic@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	alsa-devel@alsa-project.org
Subject: Re: [PATCH v2 0/2] ASoC: meson: aiu: fix duplicate debugfs directory error
Date: Wed, 06 Apr 2022 14:28:50 +0100	[thread overview]
Message-ID: <164925173019.83821.614218458873558335.b4-ty@kernel.org> (raw)
In-Reply-To: <51953618-79b6-0df7-2d28-d5dce4dc86c7@gmail.com>

On Wed, 9 Mar 2022 21:20:01 +0100, Heiner Kallweit wrote:
> On a S905W-based system I get the following error:
> debugfs: Directory 'c1105400.audio-controller' with parent 'P230-Q200' already present!
> 
> Turned out that multiple components having the same name triggers this
> error in soc_init_component_debugfs(). The proposed solution allows
> other drivers to adopt the same approach with minimal effort.
> With the patch the error is gone and that's the debugfs entries.
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: soc-core: add debugfs_prefix member to snd_soc_component_driver
      commit: d462f6ed2aeac30c0b440a91fb05d964956935f9
[2/2] ASoC: meson: aiu: fix duplicate debugfs directory error
      commit: 89bac792faf03fae5a9564bebfaacab53a029932

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

_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

      parent reply	other threads:[~2022-04-06 13:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-09 20:20 Heiner Kallweit
2022-03-09 20:21 ` [PATCH v2 1/2] ASoC: soc-core: add debugfs_prefix member to snd_soc_component_driver Heiner Kallweit
2022-03-09 20:23 ` [PATCH v2 2/2] ASoC: meson: aiu: fix duplicate debugfs directory error Heiner Kallweit
2022-03-31  5:56 ` [PATCH v2 0/2] " Heiner Kallweit
2022-04-05 18:08   ` Mark Brown
2022-04-06 13:28 ` 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=164925173019.83821.614218458873558335.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=hkallweit1@gmail.com \
    --cc=jbrunet@baylibre.com \
    --cc=khilman@baylibre.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=narmstrong@baylibre.com \
    --cc=perex@perex.cz \
    --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®