FAILED: patch "[PATCH] ASoC: sta32x: set ->component pointer in private struct" failed to apply to 4.14-stable tree
Subsystems (3)
[email protected]
maintainerThe patch below does not apply to the 4.14-stable tree.
If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to <[email protected]>.
thanks,
greg k-h
------------------ original commit in Linus's tree ------------------
Quoted 1 line
From
747df19747bc9752cd40b9cce761e17a033aa5c2Mon Sep 17 00:00:00 2001
From: Daniel Mack <[email protected]>
Date: Thu, 11 Oct 2018 20:32:05 +0200
Subject: [PATCH] ASoC: sta32x: set ->component pointer in private struct
The ESD watchdog code in sta32x_watchdog() dereferences the pointer which is never assigned.
This is a regression from a1be4cead9b950 ("ASoC: sta32x: Convert to direct regmap API usage.") which went unnoticed since nobody seems to use that ESD workaround.
sound/soc/codecs/sta32x.c +3 -0
@@ -879,6 +879,9 @@ static int sta32x_probe(struct snd_soc_component *component)struct sta32x_priv *sta32x =snd_soc_component_get_drvdata (component);struct sta32x_platform_data *pdata = sta32x->pdata;int i, ret =0 , thermal =0 ; + + sta32x->component = component; + ret =regulator_bulk_enable (ARRAY_SIZE (sta32x->supplies), sta32x->supplies);if (ret !=0 ) {
Quoted 5 lines · On Sun, Nov 11, 2018 at 06:29:26AM -0800, [email protected] wrote:
The patch below does not apply to the 4.14-stable tree.
If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to <[email protected]>.
The attached backported patch will apply to 4.14-stable tree. But I will prefer to wait for Mark or Daniel to confirm that I have not done something foolish.
--
Regards
Sudip
Quoted 1 line
From
8a3172ca525a0a990ddd739c8969129eaaad859fMon Sep 17 00:00:00 2001
From: Daniel Mack <[email protected]>
Date: Thu, 11 Oct 2018 20:32:05 +0200
Subject: [PATCH] ASoC: sta32x: set ->component pointer in private struct
commit 747df19747bc9752cd40b9cce761e17a033aa5c2 upstream
The ESD watchdog code in sta32x_watchdog() dereferences the pointer which is never assigned.
This is a regression from a1be4cead9b950 ("ASoC: sta32x: Convert to direct regmap API usage.") which went unnoticed since nobody seems to use that ESD workaround.
--- sound/soc/codecs/sta32x.c | 3 +++ 1 file changed, 3 insertions(+)
sound/soc/codecs/sta32x.c +3 -0
@@ -879,6 +879,9 @@ static int sta32x_probe(struct snd_soc_codec *codec)struct sta32x_priv *sta32x =snd_soc_codec_get_drvdata (codec);struct sta32x_platform_data *pdata = sta32x->pdata;int i, ret =0 , thermal =0 ; + + sta32x->codec = codec; + ret =regulator_bulk_enable (ARRAY_SIZE (sta32x->supplies), sta32x->supplies);if (ret !=0 ) {
Signature · 1 line
2.11.0
Mark Brown
maintainerQuoted 10 lines · Sudip Mukherjee
Quoted 5 lines · On Sun, Nov 11, 2018 at 06:29:26AM -0800, [email protected] wrote:
The patch below does not apply to the 4.14-stable tree.
If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to <[email protected]>.The attached backported patch will apply to 4.14-stable tree. But I will prefer to wait for Mark or Daniel to confirm that I have not done something foolish.
Should be fine from a quick scan.
Quoted 10 lines · Sudip Mukherjee
Quoted 5 lines · On Sun, Nov 11, 2018 at 06:29:26AM -0800, [email protected] wrote:
The patch below does not apply to the 4.14-stable tree.
If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to <[email protected]>.The attached backported patch will apply to 4.14-stable tree. But I will prefer to wait for Mark or Daniel to confirm that I have not done something foolish.
Yes, LGTM.
Thanks!
Daniel
Quoted 8 lines · Daniel Mack
Quoted 7 lines · Sudip Mukherjee
Quoted 5 lines · On Sun, Nov 11, 2018 at 06:29:26AM -0800, [email protected] wrote:
The patch below does not apply to the 4.14-stable tree.
If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to <[email protected]>.
Quoted 5 lines
Quoted 3 lines
The attached backported patch will apply to 4.14-stable tree. But I will prefer to wait for Mark or Daniel to confirm that I have not done something foolish.
Yes, LGTM.
Queued for all but 3.18, thanks all.
--
Thanks,
Sasha
Greg KH
maintainerQuoted 9 lines · Sasha Levin
Quoted 8 lines · Daniel Mack
Quoted 7 lines · Sudip Mukherjee
Quoted 5 lines · On Sun, Nov 11, 2018 at 06:29:26AM -0800, [email protected] wrote:
The patch below does not apply to the 4.14-stable tree.
If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to <[email protected]>.
Quoted 7 lines
Quoted 5 lines
Quoted 3 lines
The attached backported patch will apply to 4.14-stable tree. But I will prefer to wait for Mark or Daniel to confirm that I have not done something foolish.
Yes, LGTM.
Queued for all but 3.18, thanks all.
It breaks the build on 4.4 and 4.9, so I've dropped it from there :(
thanks,
greg k-h