From: Bjorn Andersson <andersson@kernel.org>
To: konrad.dybcio@linaro.org, Mukesh Ojha <quic_mojha@quicinc.com>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: (subset) [PATCH v2 1/4] firmware: qcom: scm: Remove log reporting memory allocation failure
Date: Sun, 21 Apr 2024 17:29:27 -0500 [thread overview]
Message-ID: <171373856759.1196479.1054868371443084757.b4-ty@kernel.org> (raw)
In-Reply-To: <1711034642-22860-1-git-send-email-quic_mojha@quicinc.com>
On Thu, 21 Mar 2024 20:53:59 +0530, Mukesh Ojha wrote:
> Remove redundant memory allocation failure.
>
> WARNING: Possible unnecessary 'out of memory' message
> + if (!mdata_buf) {
> + dev_err(__scm->dev, "Allocation of metadata buffer failed.\n");
>
>
> [...]
Applied, thanks!
[1/4] firmware: qcom: scm: Remove log reporting memory allocation failure
commit: 3de990f7895906a7a18d2dff63e3e525acaa4ecc
[2/4] firmware: scm: Remove redundant scm argument from qcom_scm_waitq_wakeup()
commit: 000636d91d605f6209a635a29d0487af5b12b237
[3/4] firmware: qcom: scm: Rework dload mode availability check
commit: 398a4c58f3f29ac3ff4d777dc91fe40a07bbca8c
[4/4] firmware: qcom: scm: Fix __scm and waitq completion variable initialization
commit: 2e4955167ec5c04534cebea9e8273a907e7a75e1
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2024-04-21 22:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 15:23 Mukesh Ojha
2024-03-21 15:24 ` [PATCH v2 2/4] firmware: scm: Remove redundant scm argument from qcom_scm_waitq_wakeup() Mukesh Ojha
2024-03-22 18:22 ` Konrad Dybcio
2024-03-21 15:24 ` [PATCH v2 3/4] firmware: qcom: scm: Rework dload mode availability check Mukesh Ojha
2024-03-22 18:24 ` Konrad Dybcio
2024-03-21 15:24 ` [PATCH v2 4/4] firmware: qcom: scm: Fix __scm and waitq completion variable initialization Mukesh Ojha
2024-04-05 15:40 ` [PATCH v2 1/4] firmware: qcom: scm: Remove log reporting memory allocation failure Mukesh Ojha
2024-04-21 22:29 ` Bjorn Andersson [this message]
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=171373856759.1196479.1054868371443084757.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_mojha@quicinc.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
all inboxes | Powered by JetHome®