[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2c43966d-33da-107a-ff47-370e3e27a99a@linaro.org>
Date: Mon, 31 Jul 2023 10:23:56 +0200
From: Konrad Dybcio <konrad.dybcio@...aro.org>
To: Bjorn Andersson <quic_bjorande@...cinc.com>,
Bjorn Andersson <andersson@...nel.org>, Chris Lew <quic_clew@...cinc.com>
Cc: Alex Elder <elder@...nel.org>, "David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Mathieu Poirier <mathieu.poirier@...aro.org>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org,
linux-remoteproc@...r.kernel.org
Subject: Re: [PATCH 4/4] soc: qcom: aoss: Tidy up qmp_send() callers
On 31.07.2023 06:10, Bjorn Andersson wrote:
> With qmp_send() handling variable length messages and string formatting
> he callers of qmp_send() can be cleaned up to not care about these
> things.
>
> Drop the QMP_MSG_LEN sized buffers and use the message formatting, as
> appropriate.
>
> Signed-off-by: Bjorn Andersson <quic_bjorande@...cinc.com>
> ---
If Alex is okay with that going through qcom:
Reviewed-by: Konrad Dybcio <konrad.dybcio@...aro.org>
One nit below.
[...]
> - snprintf(buf, sizeof(buf),
> - "{class: volt_flr, event:zero_temp, res:%s, value:%s}",
> - qmp_cdev->name,
> - cdev_state ? "on" : "off");
> -
> - ret = qmp_send(qmp_cdev->qmp, buf);
> -
> + ret = qmp_send(qmp_cdev->qmp, "{class: volt_flr, event:zero_temp, res:%s, value:%s}",
There's a space after the first colon but not after the subsequent
ones.
Konrad
Powered by blists - more mailing lists