From: Mark Brown <broonie@kernel.org>
To: Ross Zwisler <zwisler@chromium.org>
Cc: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
linux-kernel@vger.kernel.org, Ross Zwisler <zwisler@google.com>,
Jaroslav Kysela <perex@perex.cz>,
Jie Yang <yang.jie@linux.intel.com>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Takashi Iwai <tiwai@suse.com>,
alsa-devel@alsa-project.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] ASoC: Intel: avoid Oops if DMA setup fails
Date: Fri, 3 May 2019 13:34:06 +0900 [thread overview]
Message-ID: <20190503043406.GZ14916@sirena.org.uk> (raw)
In-Reply-To: <20190429182517.210909-1-zwisler@google.com>
[-- Attachment #1: Type: text/plain, Size: 373 bytes --]
On Mon, Apr 29, 2019 at 12:25:17PM -0600, Ross Zwisler wrote:
> Currently in sst_dsp_new() if we get an error return from sst_dma_new()
> we just print an error message and then still complete the function
> successfully. This means that we are trying to run without sst->dma
Please don't bury patches in the replies to existing threads, it makes
it harder to spot them.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-05-03 4:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 16:47 [PATCH] " Ross Zwisler
2019-04-26 21:03 ` Pierre-Louis Bossart
2019-04-29 17:02 ` Ross Zwisler
2019-04-29 18:25 ` [PATCH v2] " Ross Zwisler
2019-04-29 18:45 ` Pierre-Louis Bossart
2019-05-03 4:34 ` Mark Brown [this message]
2019-05-03 6:18 ` Applied "ASoC: Intel: avoid Oops if DMA setup fails" to the asoc tree Mark Brown
2019-05-03 6:21 ` Mark Brown
2019-05-03 6:23 ` Mark Brown
[not found] ` <20190426185246.AD8E5206A3@mail.kernel.org>
2019-04-29 18:27 ` [PATCH] ASoC: Intel: avoid Oops if DMA setup fails Ross Zwisler
2019-05-03 19:45 ` [linux-4.4.y PATCH] " Ross Zwisler
2019-05-05 13:15 ` Greg KH
2019-05-09 17:41 ` Greg KH
2019-05-09 18:11 ` Ross Zwisler
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=20190503043406.GZ14916@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=stable@vger.kernel.org \
--cc=tiwai@suse.com \
--cc=yang.jie@linux.intel.com \
--cc=zwisler@chromium.org \
--cc=zwisler@google.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®