From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Sasha Levin <sashal@kernel.org>,
Roman Demidov <roman.demidov.nn@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Tim Guttzeit <t.guttzeit@tuxedocomputers.com>,
Werner Sembach <wse@tuxedocomputers.com>,
Kailang Yang <kailang@realtek.com>,
Zhang Heng <zhangheng@kylinos.cn>,
Sean Rhodes <sean@starlabs.systems>,
Damien Dagorn <damien.dagorn29@gmail.com>,
Martin Hamilton <m@martinh.net>,
Bharat Dev Burman <bharat.singh7924@gmail.com>,
Lei Huang <huanglei@kylinos.cn>,
Stefan Binding <sbinding@opensource.cirrus.com>,
Lucas Tanure <tanureal@opensource.cirrus.com>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
Denis Arefev <arefev@swemel.ru>, Takashi Iwai <tiwai@suse.de>
Subject: Re: [PATCH 6.1] ALSA: hda: Fix missing pointer check in hda_component_manager_init function
Date: Mon, 14 Sep 2026 22:03:35 -0400 [thread overview]
Message-ID: <daily-reply-0019-re-alsa-hda-component-match-6-1@kernel.org> (raw)
In-Reply-To: <20260914080546.11947-1-roman.demidov.nn@gmail.com>
> [Roman: Instead of modifying hda_component_manager_init() (which does not
> yet exist in version 6.1), a check needs to be added to the
> cs35l41_generic_fixup() function
6.6 is missing 1cf11d80db5d ("ALSA: hda: Fix missing pointer check in
hda_component_manager_init function") as well, and it is the newer tree, so 6.1
cannot go first here.
A 6.6 version also needs one more hunk than this: 6.6 has a second unguarded
component_match_add() in tas2781_generic_fixup() alongside the
cs35l41_generic_fixup() one.
Could you send a v2 covering 6.6, both call sites, and 6.1?
--
Thanks,
Sasha
prev parent reply other threads:[~2026-09-15 2:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 8:05 Roman Demidov
2026-09-15 2:03 ` Sasha Levin [this message]
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=daily-reply-0019-re-alsa-hda-component-match-6-1@kernel.org \
--to=sashal@kernel.org \
--cc=arefev@swemel.ru \
--cc=bharat.singh7924@gmail.com \
--cc=damien.dagorn29@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=huanglei@kylinos.cn \
--cc=kailang@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=m@martinh.net \
--cc=perex@perex.cz \
--cc=roman.demidov.nn@gmail.com \
--cc=sbinding@opensource.cirrus.com \
--cc=sean@starlabs.systems \
--cc=stable@vger.kernel.org \
--cc=t.guttzeit@tuxedocomputers.com \
--cc=tanureal@opensource.cirrus.com \
--cc=tiwai@suse.com \
--cc=tiwai@suse.de \
--cc=wse@tuxedocomputers.com \
--cc=zhangheng@kylinos.cn \
/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®