From: Vinod Koul <vkoul@kernel.org>
To: Srinivasa Rao Mandadapu <quic_srivasam@quicinc.com>
Cc: agross@kernel.org, bjorn.andersson@linaro.org,
lgirdwood@gmail.com, broonie@kernel.org, robh+dt@kernel.org,
quic_plai@quicinc.com, bgoswami@codeaurora.org, perex@perex.cz,
tiwai@suse.com, srinivas.kandagatla@linaro.org,
rohitkr@codeaurora.org, linux-arm-msm@vger.kernel.org,
alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, swboyd@chromium.org,
judyhsiao@chromium.org, yung-chuan.liao@linux.intel.com,
pierre-louis.bossart@linux.intel.com, sanyog.r.kale@intel.com,
Venkata Prasad Potturu <quic_potturu@quicinc.com>
Subject: Re: [PATCH v6 2/3] soundwire: qcom: constify static struct qcom_swrm_data global variables
Date: Wed, 2 Mar 2022 21:19:10 +0530 [thread overview]
Message-ID: <Yh+R9kcqytMhhiWU@matsya> (raw)
In-Reply-To: <1646224982-3361-3-git-send-email-quic_srivasam@quicinc.com>
On 02-03-22, 18:13, Srinivasa Rao Mandadapu wrote:
> The qcom_swrm_data structures is only required for setting soundwire params,
> so make the qcom_swrm_data structure const to allow the compiler
> to put it in read-only memory and avoid unintentional modifications.
Applied, thanks
--
~Vinod
next prev parent reply other threads:[~2022-03-02 15:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 12:42 [PATCH v6 0/3] Add support for SoundWire1.6 audio cgcr register control Srinivasa Rao Mandadapu
2022-03-02 12:43 ` [PATCH v6 1/3] soundwire: qcom: Add compatible name for v1.6.0 Srinivasa Rao Mandadapu
2022-03-02 15:43 ` Vinod Koul
2022-03-03 1:51 ` Srinivasa Rao Mandadapu
2022-03-02 12:43 ` [PATCH v6 2/3] soundwire: qcom: constify static struct qcom_swrm_data global variables Srinivasa Rao Mandadapu
2022-03-02 15:49 ` Vinod Koul [this message]
2022-03-02 12:43 ` [PATCH v6 3/3] dt-bindings: soundwire: qcom: Add bindings for audio CSR reset control property Srinivasa Rao Mandadapu
2022-03-02 15:48 ` Vinod Koul
2022-03-03 1:56 ` Srinivasa Rao Mandadapu
2022-03-02 17:41 ` Rob Herring
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=Yh+R9kcqytMhhiWU@matsya \
--to=vkoul@kernel.org \
--cc=agross@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bgoswami@codeaurora.org \
--cc=bjorn.andersson@linaro.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=judyhsiao@chromium.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=quic_plai@quicinc.com \
--cc=quic_potturu@quicinc.com \
--cc=quic_srivasam@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=rohitkr@codeaurora.org \
--cc=sanyog.r.kale@intel.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=swboyd@chromium.org \
--cc=tiwai@suse.com \
--cc=yung-chuan.liao@linux.intel.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