From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] ALSA: pcm: Fix potential Spectre v1 vulnerability
Date: Wed, 12 Dec 2018 22:25:16 +0000 [thread overview]
Message-ID: <20181212222517.961072084E@mail.kernel.org> (raw)
In-Reply-To: <20181212213628.GA29911@embeddedor>
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: v4.19.8, v4.14.87, v4.9.144, v4.4.166, v3.18.128,
v4.19.8: Build OK!
v4.14.87: Build OK!
v4.9.144: Failed to apply! Possible dependencies:
2c4842d3b6b3 ("ALSA: pcm: add local header file for snd-pcm module")
v4.4.166: Failed to apply! Possible dependencies:
2c4842d3b6b3 ("ALSA: pcm: add local header file for snd-pcm module")
v3.18.128: Failed to apply! Possible dependencies:
2c4842d3b6b3 ("ALSA: pcm: add local header file for snd-pcm module")
90bbaf66ee7b ("ALSA: timer: add config item to export PCM timer disabling for expert")
9bc889b4ba88 ("ALSA: pcm: Update the state properly before notification")
f5914908a5b7 ("ALSA: pcm: Replace PCM hwptr tracking with tracepoints")
How should we proceed with this patch?
--
Thanks,
Sasha
next prev parent reply other threads:[~2018-12-12 22:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 21:36 [PATCH] ALSA: pcm: Fix potential Spectre v1 vulnerability Gustavo A. R. Silva
2018-12-12 22:25 ` Sasha Levin [this message]
2018-12-13 8:15 ` Takashi Iwai
2018-12-13 8:15 ` Takashi Iwai
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=20181212222517.961072084E@mail.kernel.org \
--to=sashal@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=gustavo@embeddedor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=stable@vger.kernel.org \
--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.