From: "Sheetal ." <sheetal@nvidia.com>
To: "Péter Ujfalusi" <peter.ujfalusi@linux.intel.com>,
"Sameer Pujar" <spujar@nvidia.com>,
broonie@kernel.org, lgirdwood@gmail.com, perex@perex.cz,
tiwai@suse.com, linux-sound@vger.kernel.org,
pierre-louis.bossart@linux.intel.com,
ranjani.sridharan@linux.intel.com
Cc: linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
jonathanh@nvidia.com, thierry.reding@gmail.com,
mkumard@nvidia.com
Subject: Re: [RFC PATCH v2] ASoC: soc-pcm: Optimize hw_params() BE DAI call
Date: Wed, 21 May 2025 17:03:22 +0530 [thread overview]
Message-ID: <35ac71b7-2b75-4a33-8e36-28b905690b02@nvidia.com> (raw)
In-Reply-To: <72b3954d-55d5-45ed-8a51-c0b1edd3783c@linux.intel.com>
On 21-05-2025 13:47, Péter Ujfalusi wrote:
> External email: Use caution opening links or attachments
>
>
> On 21/05/2025 08:25, Sheetal . wrote:
>>>
>>> Picked the patch to run it through our CI:
>>> https://github.com/thesofproject/linux/pull/5414
>>
>> Please share feedback or comments if any.
>
> sorry fort he delay, but we have CI maintenance and movement.
>
> The patch looks good and makes sense, it was just hard to tell from the
> commit message what is the reason for it.
Thanks for the feedback. I will send [RFC PATCH v3] with the refined
commit message.
>
> Reviewed-by: Peter Ujfalusi <peter.ujflausi@linux.intel.com>
>
next prev parent reply other threads:[~2025-05-21 11:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 8:30 [RFC PATCH v2] ASoC: soc-pcm: Optimize hw_params() BE DAI call Sheetal .
2025-04-08 9:04 ` Sheetal .
2025-05-12 12:01 ` Sameer Pujar
2025-05-13 6:15 ` Péter Ujfalusi
2025-05-21 5:25 ` Sheetal .
2025-05-21 8:17 ` Péter Ujfalusi
2025-05-21 11:33 ` Sheetal . [this message]
2025-05-13 11:10 ` Péter Ujfalusi
2025-05-23 9:55 ` Pierre-Louis Bossart
2025-05-23 11:01 ` Sheetal .
2025-05-26 16:18 ` Pierre-Louis Bossart
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=35ac71b7-2b75-4a33-8e36-28b905690b02@nvidia.com \
--to=sheetal@nvidia.com \
--cc=broonie@kernel.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=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=spujar@nvidia.com \
--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