[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a3efee22-622f-438b-a10e-7896fbcd8c0f@codeaurora.org>
Date: Fri, 27 Nov 2020 23:40:52 +0530
From: Srinivasa Rao Mandadapu <srivasam@...eaurora.org>
To: Mark Brown <broonie@...nel.org>
Cc: agross@...nel.org, bjorn.andersson@...aro.org, lgirdwood@...il.com,
robh+dt@...nel.org, plai@...eaurora.org, bgoswami@...eaurora.org,
perex@...ex.cz, tiwai@...e.com, srinivas.kandagatla@...aro.org,
rohitkr@...eaurora.org, linux-arm-msm@...r.kernel.org,
alsa-devel@...a-project.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org,
V Sujith Kumar Reddy <vsujithk@...eaurora.org>
Subject: Re: [PATCH] Asoc: qcom: Fix for problem in resume with CRAS
Thanks MarkĀ for your time!!!
On 11/27/2020 6:08 PM, Mark Brown wrote:
> On Fri, Nov 27, 2020 at 09:42:03AM +0530, Srinivasa Rao Mandadapu wrote:
>> To support playback continuation after resume problem in chrome
>> audio server:
>> Prepare device in platform trigger callback.
>> Make I2s and DMA control registers as non volatile.
> What is the actual issue this is fixing?
Please ignore this patch. Posted new version of patch( [PATCH v3] ASoC:
qcom: Fix playback recover problem in suspend resume) instead of this.
>
> As I have previously said please submit patches using subject lines
> reflecting the style for the subsystem, this makes it easier for people
> to identify relevant patches. Look at what existing commits in the area
> you're changing are doing and make sure your subject lines visually
> resemble what they're doing. There's no need to resubmit to fix this
> alone.
Previously I could not understand what is the mistake in subject line.
Now I understood
the mistake and will take care of it next time.
--
Qualcomm India Private Limited, on behalf of Qualcomm Innovation Center, Inc.,
is a member of Code Aurora Forum, a Linux Foundation Collaborative Project.
Powered by blists - more mailing lists