From: "Sheetal ." <sheetal@nvidia.com>
To: Mark Brown <broonie@kernel.org>
Cc: Sander Vanheule <sander@svanheule.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Mohan kumar <mkumard@nvidia.com>,
linux-kernel@vger.kernel.org, linux-sound@vger.kernel.org,
linux-tegra@vger.kernel.org
Subject: Re: [RFC PATCH v2 3/3] ASoC: tegra: Enable flat_cache_default_is_zero for audio drivers
Date: Mon, 12 Jan 2026 18:23:39 +0530 [thread overview]
Message-ID: <cfa7045d-bec6-4b3c-8413-fbcf1f1543e5@nvidia.com> (raw)
In-Reply-To: <bea00d79-35df-43f8-8a3c-62d6db7952ef@sirena.org.uk>
On 12-01-2026 17:56, Mark Brown wrote:
> On Mon, Jan 12, 2026 at 09:58:41AM +0530, Sheetal . wrote:
>> From: Sheetal <sheetal@nvidia.com>
>>
>> Set flat_cache_default_is_zero flag in Tegra audio driver regmap
>> configurations.
>
> This doesn't apply against current code, please check and resend.
As mentioned in the commit message,
This patch depends on:
https://patchwork.ozlabs.org/project/linux-tegra/patch/20251217132524.2844499-1-sheetal@nvidia.com/.
Kindly let me know if any additional action is required on my part.
Regards,
Sheetal
next prev parent reply other threads:[~2026-01-12 12:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 4:28 [RFC PATCH v2 0/3] regmap: Add flat_cache_default_is_zero flag for flat cache Sheetal .
2026-01-12 4:28 ` [RFC PATCH v2 1/3] " Sheetal .
2026-01-12 19:09 ` Sander Vanheule
2026-01-12 21:45 ` Mark Brown
2026-01-12 4:28 ` [RFC PATCH v2 2/3] regmap: Add KUnit test for flat_cache_default_is_zero Sheetal .
2026-01-12 4:28 ` [RFC PATCH v2 3/3] ASoC: tegra: Enable flat_cache_default_is_zero for audio drivers Sheetal .
2026-01-12 12:26 ` Mark Brown
2026-01-12 12:53 ` Sheetal . [this message]
2026-01-12 13:32 ` 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=cfa7045d-bec6-4b3c-8413-fbcf1f1543e5@nvidia.com \
--to=sheetal@nvidia.com \
--cc=broonie@kernel.org \
--cc=dakr@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mkumard@nvidia.com \
--cc=perex@perex.cz \
--cc=rafael@kernel.org \
--cc=sander@svanheule.net \
--cc=thierry.reding@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox