From: Mark Brown <broonie@kernel.org>
To: lgirdwood@gmail.com, alsa-devel@alsa-project.org,
mnlife <mnlife@126.com>
Subject: Re: [PATCH] ASoC: soc-jack: calling snd_soc_jack_report causes a null pointer access
Date: Tue, 15 Aug 2023 19:09:13 +0100 [thread overview]
Message-ID: <169212295378.59295.3979482452886622652.b4-ty@kernel.org> (raw)
In-Reply-To: <20230811142511.6570-1-mnlife@126.com>
On Fri, 11 Aug 2023 22:25:11 +0800, mnlife wrote:
> When snd_soc_card_jack_new is not called or the call fails,
> calling this function causes a null pointer access
>
>
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: soc-jack: calling snd_soc_jack_report causes a null pointer access
commit: 62cc82e6486b9b66b340bbf5fb38b0171fb56a7f
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
next prev parent reply other threads:[~2023-08-15 18:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 14:25 [PATCH] ASoC: soc-jack: calling snd_soc_jack_report causes a null pointer access mnlife
2023-08-15 18:09 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-07-19 3:08 mnlife qiao
[not found] <tencent_2D17145034BA02B43C169473C02C4257AF06@qq.com>
2020-07-19 2:52 ` mnlife qiao
2020-07-18 14:56 mnlife
[not found] <5f0e49da.1c69fb81.1ede7.a8fbSMTPIN_ADDED_MISSING@mx.google.com>
2020-07-15 0:24 ` mnlife qiao
2020-07-16 22:29 ` Mark Brown
2020-07-16 22:29 ` 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=169212295378.59295.3979482452886622652.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=lgirdwood@gmail.com \
--cc=mnlife@126.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.