From: Sasha Levin <sashal@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-stable <stable@vger.kernel.org>
Cc: Sasha Levin <sashal@kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"Sheetal ." <sheetal@nvidia.com>,
Jon Hunter <jonathanh@nvidia.com>
Subject: Re: stable request: 7.2.y: Fix audio support for 64-bit Tegra devices
Date: Wed, 2 Sep 2026 18:14:01 -0400 [thread overview]
Message-ID: <20260902-daily-reply-0002-tegra-audio-7-2@kernel.org> (raw)
In-Reply-To: <cabc530b-3504-4243-86f9-19c57ceae514@nvidia.com>
> Audio support for 64-bit Tegra devices is currently broken
> for Linux v7.2 after commit 4b05ccb17f92 ("regcache: Sort
> the local copy of an unsorted reg_defaults array") landed
> exposing a bug in the Tegra audio drivers.
>
> This has now been fixed by the following mainline commits
> and I would like to include these in the linux-7.2.y branch
> if possible.
Queued for 7.2, thanks.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-09-02 22:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 16:54 stable request: 7.2.y: Fix audio support for 64-bit Tegra devices Jon Hunter
2026-09-02 22:14 ` 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=20260902-daily-reply-0002-tegra-audio-7-2@kernel.org \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=linux-tegra@vger.kernel.org \
--cc=sheetal@nvidia.com \
--cc=stable@vger.kernel.org \
/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