From: Mark Brown <broonie@kernel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: John Stultz <john.stultz@linaro.org>,
Takashi Iwai <tiwai@suse.de>, Liam Girdwood <lgirdwood@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Bard Liao <yung-chuan.liao@linux.intel.com>,
Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>,
Srini Kandagatla <srinivas.kandagatla@linaro.org>,
Vinod Koul <vinod.koul@linaro.org>,
Amit Pundir <amit.pundir@linaro.org>
Subject: Re: [GIT PULL] sound fixes for 5.8-rc1
Date: Fri, 12 Jun 2020 15:46:46 +0100 [thread overview]
Message-ID: <20200612144646.GJ5396@sirena.org.uk> (raw)
In-Reply-To: <7cd79261-6f8d-cad0-c65b-57570a40a6b6@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 959 bytes --]
On Fri, Jun 12, 2020 at 08:54:11AM -0500, Pierre-Louis Bossart wrote:
> I think that those configuration errors are the problem and should be fixed
> as a prerequisite to the removal of the duplication between
> dpcm_playback/dpcm_capture/playback_only/capture_only. it may be painful and
> generate noise for a while, but if we only throw a warning what are the odds
> all those configuration errors will eventually be fixed?
Yeah, I'm kind of pessimistic about the likelyhood of people paying
attention to warnings.
> If we need more time for validation on all platforms, then maybe we can
> first relax the check for 5.8-rc1 as suggested by John, but re-add the
> -EINVAL on -next to give a target of 5.9 with all configurations fixed?
I can't help feeling that it'd be postponing the inevitable, but perhaps
I'm being overly pessimistic here. The change did obviously go in quite
late though so it's not the worst idea if you want to send the patch?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-06-12 14:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 11:33 Takashi Iwai
2020-06-11 19:50 ` pr-tracker-bot
2020-06-12 0:13 ` John Stultz
2020-06-12 0:49 ` John Stultz
2020-06-12 11:41 ` Srinivas Kandagatla
2020-06-12 12:35 ` Mark Brown
2020-06-12 23:59 ` John Stultz
2020-06-12 12:19 ` Mark Brown
2020-06-12 13:54 ` Pierre-Louis Bossart
2020-06-12 14:46 ` Mark Brown [this message]
2020-06-12 14:56 ` Pierre-Louis Bossart
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=20200612144646.GJ5396@sirena.org.uk \
--to=broonie@kernel.org \
--cc=amit.pundir@linaro.org \
--cc=guennadi.liakhovetski@linux.intel.com \
--cc=john.stultz@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=tiwai@suse.de \
--cc=vinod.koul@linaro.org \
--cc=yung-chuan.liao@linux.intel.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®