From: Mark Brown <broonie@kernel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org
Subject: Re: [PATCH 00/19] ASoC: SOF: improvements for ABI checks and Intel code
Date: Tue, 7 May 2019 12:04:46 +0900 [thread overview]
Message-ID: <20190507030446.GD14916@sirena.org.uk> (raw)
In-Reply-To: <cf4cf0ca-b11d-48ff-8e23-fd2e308ec3af@linux.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 835 bytes --]
On Mon, May 06, 2019 at 09:59:24AM -0500, Pierre-Louis Bossart wrote:
> On 5/5/19 10:51 PM, Mark Brown wrote:
> > The last point there is that Intel only write patches, nobody from Intel
> > is reviewing other people's patches especially in areas of the code like
> > DPCM which are complex, fragile and where Intel is by far the most
> > active user.
> It's a valid point, and for now we indeed only check for non-regressions and
> provide point solutions without looking at the bigger picture. We have a
> couple of people ramping up (Ranjani, Libin, Guennadi, Jaska) and hopefully
> at some point we'll be able to review and improve.
Even just testing (rather than reviewing, though obviously reviewing
would be good!) patches off the list would be very helpful and is close
to the regression testing stuff you're already doing.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2019-05-07 3:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 23:09 [PATCH 00/19] ASoC: SOF: improvements for ABI checks and Intel code Pierre-Louis Bossart
2019-04-30 23:09 ` [PATCH 01/19] ASoC: SOF: add Kconfig option for strict ABI checks Pierre-Louis Bossart
2019-04-30 23:09 ` [PATCH 02/19] ASOC: SOF: ipc: add support for stricter " Pierre-Louis Bossart
2019-04-30 23:09 ` [PATCH 03/19] ASoC: SOF: topology: " Pierre-Louis Bossart
2019-04-30 23:09 ` [PATCH 04/19] ASoC: SOF: Intel: cnl: add pointer ops to use DPIB position Pierre-Louis Bossart
2019-04-30 23:09 ` [PATCH 05/19] ASoC: SOF: Intel: hda: add the SSP Host Device memory space Pierre-Louis Bossart
2019-04-30 23:09 ` [PATCH 06/19] ASoC: SOF: Intel: hda: add SSP info to the chip info struct Pierre-Louis Bossart
2019-04-30 23:09 ` [PATCH 07/19] ASoC: SOF: Intel: hda: set I2S slave before enabling DSP Pierre-Louis Bossart
2019-04-30 23:09 ` [PATCH 08/19] ASoC: SOF: Intel: hda: set bus->idx as 0 Pierre-Louis Bossart
2019-04-30 23:09 ` [PATCH 09/19] ASoC: SOF: Intel: hda-pcm: remove useless dependency on hdac_ext Pierre-Louis Bossart
2019-04-30 23:09 ` [PATCH 10/19] ASoC: SOF: PCM: add period_elapsed work to fix race condition in interrupt context Pierre-Louis Bossart
2019-04-30 23:09 ` [PATCH 11/19] ASoC: SOF: Intel: use snd_sof_pcm_period_elapsed Pierre-Louis Bossart
2019-04-30 23:09 ` [PATCH 12/19] ASoC: SOF: ipc: " Pierre-Louis Bossart
2019-04-30 23:09 ` [PATCH 13/19] ASoC: SOF: Intel: hda-ipc: simplify handling of IPC IRQ Pierre-Louis Bossart
2019-04-30 23:09 ` [PATCH 14/19] ASoC: SOF: Intel: hda-stream: store stream capabilities Pierre-Louis Bossart
2019-04-30 23:09 ` [PATCH 15/19] ASoC: SOF: Intel: hda-stream: handle real stream interrupts only Pierre-Louis Bossart
2019-04-30 23:09 ` [PATCH 16/19] ASoC: SOF: intel: hda: add hw_params_upon_resume flag for hda stream Pierre-Louis Bossart
2019-04-30 23:09 ` [PATCH 17/19] ASoC: SOF: IPC: add ipc dump function Pierre-Louis Bossart
2019-04-30 23:09 ` [PATCH 18/19] ASoC: SOF: Intel: APL: " Pierre-Louis Bossart
2019-04-30 23:09 ` [PATCH 19/19] ASoC: SOF: Intel: CNL: " Pierre-Louis Bossart
[not found] ` <20190503054047.GB14916@sirena.org.uk>
2019-05-03 14:47 ` [PATCH 00/19] ASoC: SOF: improvements for ABI checks and Intel code Pierre-Louis Bossart
[not found] ` <20190506035133.GI14916@sirena.org.uk>
2019-05-06 14:59 ` Pierre-Louis Bossart
2019-05-07 3:04 ` 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=20190507030446.GD14916@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--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.