stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ross Zwisler <zwisler@google.com>
To: Sasha Levin <sashal@kernel.org>
Cc: Ross Zwisler <zwisler@chromium.org>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] ASoC: Intel: avoid Oops if DMA setup fails
Date: Mon, 29 Apr 2019 12:27:10 -0600	[thread overview]
Message-ID: <20190429182710.GA209252@google.com> (raw)
In-Reply-To: <20190426185246.AD8E5206A3@mail.kernel.org>

On Fri, Apr 26, 2019 at 06:52:45PM +0000, Sasha Levin wrote:
> Hi,
> 
> [This is an automated email]
> 
> This commit has been processed because it contains a -stable tag.
> The stable tag indicates that it's relevant for the following trees: all
> 
> The bot has tested the following trees: v5.0.9, v4.19.36, v4.14.113, v4.9.170, v4.4.178, v3.18.138.
> 
> v5.0.9: Build OK!
> v4.19.36: Build OK!
> v4.14.113: Build OK!
> v4.9.170: Build OK!
> v4.4.178: Failed to apply! Possible dependencies:
>     2bd5bd15a518 ("ASoC: Intel: add bytct-rt5651 machine driver")
>     2dcffcee23a2 ("ASoC: Intel: Create independent acpi match module")
>     595788e475d0 ("ASoC: Intel: tag byt-rt5640 machine driver as deprecated")
>     95f098014815 ("ASoC: Intel: Move apci find machine routines")
>     a395bdd6b24b ("ASoC: intel: Fix sst-dsp dependency on dw stuff")
>     a92ea59b74e2 ("ASoC: Intel: sst: only select sst-firmware when DW DMAC is built-in")
>     cfffcc66a89a ("ASoC: Intel: Load the atom DPCM driver only")
> 
> v3.18.138: Failed to apply! Possible dependencies:
>     0d2135ecadb0 ("ASoC: Intel: Work around to fix HW D3 potential crash issue")
>     13735d1cecec ("ASoC: intel - kconfig: remove SND_SOC_INTEL_SST prompt")
>     161aa49ef1b9 ("ASoC: Intel: Add new dependency for Haswell machine")
>     2106241a6803 ("ASoC: Intel: create common folder and move common files in")
>     282a331fe25c ("ASoC: Intel: Add new dependency for Broadwell machine")
>     2e4f75919e5a ("ASoC: Intel: Add PM support to HSW/BDW PCM driver")
>     34084a436703 ("ASoC: intel: Remove superfluous backslash in Kconfig")
>     544c55c810a5 ("ASoC: Intel: Delete an unnecessary check before the function call "sst_dma_free"")
>     63ae1fe7739e ("ASoC: Intel: Add dependency on DesignWare DMA controller")
>     7dd6bd8926f3 ("ASoC: intel: kconfig - Move DW_DMAC_CORE dependency to machines")
>     85b88a8dd0c7 ("ASoC: Intel: Store the entry_point read from FW file")
>     9449d39b990d ("ASoC: Intel: add function to load firmware image")
>     a395bdd6b24b ("ASoC: intel: Fix sst-dsp dependency on dw stuff")
>     a92ea59b74e2 ("ASoC: Intel: sst: only select sst-firmware when DW DMAC is built-in")
>     aed3c7b77c85 ("ASoC: Intel: Add PM support to HSW/BDW IPC driver")
>     d96c53a193dd ("ASoC: Intel: Add generic support for DSP wake, sleep and stall")
>     e9600bc166d5 ("ASoC: Intel: Make ADSP memory block allocation more generic")
> 
> 
> How should we proceed with this patch?

After reviews I'll send backport patches for v4.4.X and v3.18.X as necessary.

  parent reply	other threads:[~2019-04-29 18:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-26 16:47 [PATCH] ASoC: Intel: avoid Oops if DMA setup fails 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
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   ` Ross Zwisler [this message]
2019-05-03 19:45     ` [linux-4.4.y PATCH] ASoC: Intel: avoid Oops if DMA setup fails 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=20190429182710.GA209252@google.com \
    --to=zwisler@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=zwisler@chromium.org \
    /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;
as well as URLs for NNTP newsgroup(s).