From: Mark Brown <broonie@kernel.org>
To: Jerome Brunet <jbrunet@baylibre.com>
Cc: alsa-devel@alsa-project.org,
Stephan Gerhold <stephan@gerhold.net>,
tomeu.vizoso@collabora.com, khilman@baylibre.com,
mgalka@collabora.com,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
guillaume.tucker@collabora.com, enric.balletbo@collabora.com
Subject: Re: next/master bisection: baseline.dmesg.alert on meson-sm1-sei610
Date: Fri, 17 Apr 2020 15:28:34 +0100 [thread overview]
Message-ID: <20200417142834.GF5315@sirena.org.uk> (raw)
In-Reply-To: <1j7dyeb6pt.fsf@starbuckisacylon.baylibre.com>
[-- Attachment #1: Type: text/plain, Size: 857 bytes --]
On Fri, Apr 17, 2020 at 03:08:14PM +0200, Jerome Brunet wrote:
> On Fri 17 Apr 2020 at 14:27, Mark Brown <broonie@kernel.org> wrote:
> >> Result: 9b5db059366ae ASoC: soc-pcm: dpcm: Only allow playback/capture if supported
> > This change to check the playback and capture constraints is also
> > causing issues on at least Meson - I'm a bit worried that this is also
> > causing oopses here, not just audio problems so copying in Morimoto-san
> > too. We should fix the things that are broken by this change since it's
> > a thing we should be able to rely on and do enforce for non-DPCm links
> > but I'm wondering if we should revert for 5.7 and reapply for 5.8.
> I have the device with me. I'll check an report back
Thanks! Note that the commit above got dropped from -next due to some
scripting stuff, it's in my tree or yesterday's -next.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-04-17 14:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5e997ca0.1c69fb81.f69a1.620e@mx.google.com>
2020-04-17 12:27 ` next/master bisection: baseline.dmesg.alert on meson-sm1-sei610 Mark Brown
2020-04-17 13:08 ` Jerome Brunet
2020-04-17 13:52 ` Pierre-Louis Bossart
2020-04-17 14:28 ` Mark Brown [this message]
2020-04-17 15:48 ` Jerome Brunet
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=20200417142834.GF5315@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=enric.balletbo@collabora.com \
--cc=guillaume.tucker@collabora.com \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=mgalka@collabora.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=stephan@gerhold.net \
--cc=tomeu.vizoso@collabora.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