From: Aleksei Vetrov <vvvvvv@google.com>
To: Mark Brown <broonie@kernel.org>
Cc: "Gustavo A. R. Silva" <gustavo@embeddedor.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Kees Cook <kees@kernel.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH] ASoC: dapm: fix bounds checker error in dapm_widget_list_create
Date: Tue, 29 Oct 2024 15:14:53 +0000 [thread overview]
Message-ID: <ZyD77Y8bIP3JCAZE@google.com> (raw)
In-Reply-To: <da230ccf-37b6-4e43-be12-9035c594e535@sirena.org.uk>
On Tue, Oct 29, 2024 at 02:08:32PM +0000, Mark Brown wrote:
> That doesn't seem to have shown up here?
Sorry for the mix up, I've accidentally replied in the wrong thread.
As I said in https://lore.kernel.org/all/ZyDndtgj5vKo-wvB@google.com/:
> Actually, my reply above meant to be for the nl80211 fix
> (https://lore.kernel.org/r/20241028-nl80211_parse_sched_scan-bounds-checker-fix-v1-1-bb640be0ebb7@google.com).
> For this fix I couldn't send v2, because it has been already applied by
> Mark Brown. Guess I would need to send a separate message to the stable
> team asking them to pick this patch from git.
Cheers
--
Aleksei Vetrov
next prev parent reply other threads:[~2024-10-29 15:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 22:50 [PATCH] ASoC: dapm: fix bounds checker error in dapm_widget_list_create Aleksei Vetrov
2024-10-28 22:58 ` Gustavo A. R. Silva
2024-10-28 23:45 ` Kees Cook
2024-10-29 13:37 ` Aleksei Vetrov
2024-10-29 13:47 ` Aleksei Vetrov
2024-10-29 14:08 ` Mark Brown
2024-10-29 15:14 ` Aleksei Vetrov [this message]
2024-10-29 18:15 ` Mark Brown
2024-10-29 9:50 ` Amadeusz Sławiński
2024-10-29 10:30 ` Takashi Iwai
2024-10-29 12:11 ` Amadeusz Sławiński
2024-10-29 12:21 ` Takashi Iwai
2024-10-29 12:46 ` Mark Brown
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=ZyD77Y8bIP3JCAZE@google.com \
--to=vvvvvv@google.com \
--cc=broonie@kernel.org \
--cc=gustavo@embeddedor.com \
--cc=gustavoars@kernel.org \
--cc=kees@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--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.