From: Mark Brown <broonie@kernel.org>
To: Cezary Rojewski <cezary.rojewski@intel.com>
Cc: lgirdwood@gmail.com, alsa-devel@alsa-project.org,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
tiwai@suse.com
Subject: Re: [RESEND PATCH v2 0/7] ASoC: Intel: Skylake: Driver fundaments overhaul
Date: Wed, 24 Jul 2019 19:10:22 +0100 [thread overview]
Message-ID: <20190724181022.GG4524@sirena.org.uk> (raw)
In-Reply-To: <81f9a74b-0848-8a45-a4d1-8ac44d11e0ad@intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 1076 bytes --]
On Wed, Jul 24, 2019 at 07:14:52PM +0200, Cezary Rojewski wrote:
> On 2019-07-23 20:07, Pierre-Louis Bossart wrote:
> > - draw the line at "no new features" after e.g. 5.5 and "no new
> > platforms when SOF provides a solution". SOF was expected to reach
> > feature parity by the end of 2019 so it's not a random date I just made
> > up.
> While I can agree on the "no new features" line, the date is a loose
> subject. Honestly, I could've probably called first ~70-80 patches: "a fix".
> Validation team managed to mark half scenarios a failure immediately. Then
> developers were set loose. With enough motivation, we have managed to crash
> even the most simple scenarios. I do not call a folder with bunch of code
> not following any specification, design patter, lacking verification and
> testing and confirmed to be harmful a "driver". And thus, "new features"
> gets entirely different meaning when applied to /skylake.
If there's things that fix bugs then they won't be covered by any wind
down in new features so that's a separate thing whatever happens there.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2019-07-24 18:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 14:58 [RESEND PATCH v2 0/7] ASoC: Intel: Skylake: Driver fundaments overhaul Cezary Rojewski
2019-07-23 14:58 ` [RESEND PATCH v2 1/7] ASoC: Intel: Skylake: Merge skl_sst and skl into skl_dev struct Cezary Rojewski
2019-07-24 19:17 ` Applied "ASoC: Intel: Skylake: Merge skl_sst and skl into skl_dev struct" to the asoc tree Mark Brown
2019-07-23 14:58 ` [RESEND PATCH v2 2/7] ASoC: Intel: Skylake: Combine snd_soc_skl_ipc and snd_soc_skl Cezary Rojewski
2019-07-23 14:58 ` [RESEND PATCH v2 3/7] ASoC: Intel: Skylake: Remove MCPS available check Cezary Rojewski
2019-07-24 19:17 ` Applied "ASoC: Intel: Skylake: Remove MCPS available check" to the asoc tree Mark Brown
2019-07-23 14:58 ` [RESEND PATCH v2 4/7] ASoC: Intel: Skylake: Remove memory available check Cezary Rojewski
2019-07-24 19:17 ` Applied "ASoC: Intel: Skylake: Remove memory available check" to the asoc tree Mark Brown
2019-07-23 14:58 ` [RESEND PATCH v2 5/7] ASoC: Intel: Skylake: Do not disable FW notifications Cezary Rojewski
2019-07-23 14:58 ` [RESEND PATCH v2 6/7] ASoC: Intel: Skylake: Make MCPS and CPS params obsolete Cezary Rojewski
2019-07-24 19:17 ` Applied "ASoC: Intel: Skylake: Make MCPS and CPS params obsolete" to the asoc tree Mark Brown
2019-07-23 14:58 ` [RESEND PATCH v2 7/7] ASoC: Intel: Skylake: Cleanup skl_module_cfg declaration Cezary Rojewski
2019-07-24 19:17 ` Applied "ASoC: Intel: Skylake: Cleanup skl_module_cfg declaration" to the asoc tree Mark Brown
2019-07-23 15:44 ` [RESEND PATCH v2 0/7] ASoC: Intel: Skylake: Driver fundaments overhaul Mark Brown
2019-07-23 18:07 ` Pierre-Louis Bossart
2019-07-24 16:50 ` Mark Brown
2019-07-24 17:14 ` Cezary Rojewski
2019-07-24 18:10 ` Mark Brown [this message]
2019-07-24 12:39 ` Vinod Koul
2019-07-24 12:42 ` Vinod Koul
2019-07-26 11:31 ` Cezary Rojewski
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=20190724181022.GG4524@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=cezary.rojewski@intel.com \
--cc=lgirdwood@gmail.com \
--cc=pierre-louis.bossart@linux.intel.com \
--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 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.