All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: alsa-devel@alsa-project.org,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: tiwai@suse.de, Jerome Brunet <jbrunet@baylibre.com>
Subject: Re: [PATCH] ASoC: core: use less strict tests for dailink capabilities
Date: Fri, 31 Jul 2020 19:54:44 +0100	[thread overview]
Message-ID: <159622167150.22822.3333498789357611340.b4-ty@kernel.org> (raw)
In-Reply-To: <20200723180533.220312-1-pierre-louis.bossart@linux.intel.com>

On Thu, 23 Jul 2020 13:05:33 -0500, Pierre-Louis Bossart wrote:
> Previous updates to set dailink capabilities and check dailink
> capabilities were based on a flawed assumption that all dais support
> the same capabilities as the dailink. This is true for TDM
> configurations but existing configurations use an amplifier and a
> capture device on the same dailink, and the tests would prevent the
> card from probing.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: core: use less strict tests for dailink capabilities
      commit: 4f8721542f7b75954bfad98c51aa59d683d35b50

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:[~2020-07-31 18:57 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-23 18:05 [PATCH] ASoC: core: use less strict tests for dailink capabilities Pierre-Louis Bossart
2020-07-24  8:31 ` Jerome Brunet
2020-07-24 19:05   ` Pierre-Louis Bossart
2020-07-27  9:42     ` Jerome Brunet
2020-07-27 14:13       ` Pierre-Louis Bossart
2020-07-27 15:15         ` Jerome Brunet
2020-07-27 15:26           ` Pierre-Louis Bossart
2020-07-29 15:46 ` [PATCH] ASoC: core: restore dpcm flags semantics Jerome Brunet
2020-07-29 15:46   ` Jerome Brunet
2020-07-29 15:46   ` Jerome Brunet
2020-07-29 15:56   ` Pierre-Louis Bossart
2020-07-29 15:56     ` Pierre-Louis Bossart
2020-07-29 15:56     ` Pierre-Louis Bossart
2020-07-30  9:04     ` Jerome Brunet
2020-07-30  9:04       ` Jerome Brunet
2020-07-30  9:04       ` Jerome Brunet
2020-07-30 16:06       ` Pierre-Louis Bossart
2020-07-30 16:06         ` Pierre-Louis Bossart
2020-07-30 18:52         ` Mark Brown
2020-07-30 18:52           ` Mark Brown
2020-07-30 18:52           ` Mark Brown
2020-07-31 12:16           ` Jerome Brunet
2020-07-31 12:16             ` Jerome Brunet
2020-07-31 12:16             ` Jerome Brunet
2020-07-31 17:42             ` Mark Brown
2020-07-31 17:42               ` Mark Brown
2020-07-31 17:42               ` Mark Brown
2020-07-31  8:06         ` Jerome Brunet
2020-07-31  8:06           ` Jerome Brunet
2020-07-30 18:12       ` Mark Brown
2020-07-30 18:12         ` Mark Brown
2020-07-30 18:12         ` Mark Brown
2020-07-31 18:54 ` 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=159622167150.22822.3333498789357611340.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=jbrunet@baylibre.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=tiwai@suse.de \
    /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.