From: Wei Ni <wni@nvidia.com>
To: <daniel.lezcano@linaro.org>, <edubezval@gmail.com>
Cc: <thierry.reding@gmail.com>, <linux-tegra@vger.kernel.org>,
<rui.zhang@intel.com>, <srikars@nvidia.com>,
<linux-kernel@vger.kernel.org>, <linux-pm@vger.kernel.org>,
Wei Ni <wni@nvidia.com>
Subject: [PATCH v7 2/3] thermal: tegra: fix memory allocation
Date: Thu, 3 Jan 2019 18:12:48 +0800 [thread overview]
Message-ID: <1546510369-28491-3-git-send-email-wni@nvidia.com> (raw)
In-Reply-To: <1546510369-28491-1-git-send-email-wni@nvidia.com>
Fix memory allocation to store the pointers to
thermal_zone_device.
Signed-off-by: Wei Ni <wni@nvidia.com>
Acked-by: Thierry Reding <treding@nvidia.com>
---
drivers/thermal/tegra/soctherm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/thermal/tegra/soctherm.c b/drivers/thermal/tegra/soctherm.c
index f07de8258e93..fd2703c0cfc5 100644
--- a/drivers/thermal/tegra/soctherm.c
+++ b/drivers/thermal/tegra/soctherm.c
@@ -1339,7 +1339,7 @@ static int tegra_soctherm_probe(struct platform_device *pdev)
}
tegra->thermctl_tzs = devm_kcalloc(&pdev->dev,
- soc->num_ttgs, sizeof(*z),
+ soc->num_ttgs, sizeof(z),
GFP_KERNEL);
if (!tegra->thermctl_tzs)
return -ENOMEM;
--
2.7.4
next prev parent reply other threads:[~2019-01-03 10:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 10:12 [PATCH v7 0/3] Fixes for Tegra soctherm Wei Ni
2019-01-03 10:12 ` [PATCH v7 1/3] thermal: tegra: remove unnecessary warnings Wei Ni
2019-02-18 9:47 ` Daniel Lezcano
2019-02-19 2:14 ` Wei Ni
2019-01-03 10:12 ` Wei Ni [this message]
2019-02-18 10:24 ` [PATCH v7 2/3] thermal: tegra: fix memory allocation Daniel Lezcano
2019-01-03 10:12 ` [PATCH v7 3/3] thermal: tegra: add get_trend ops Wei Ni
2019-02-18 10:27 ` Daniel Lezcano
2019-02-19 2:15 ` Wei Ni
2020-03-30 17:23 ` Daniel Lezcano
2019-01-11 2:20 ` [PATCH v7 0/3] Fixes for Tegra soctherm Wei Ni
2019-01-21 9:17 ` Wei Ni
2019-02-18 7:59 ` Wei Ni
2019-02-20 2:14 ` Zhang Rui
2019-02-20 8:42 ` Wei Ni
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=1546510369-28491-3-git-send-email-wni@nvidia.com \
--to=wni@nvidia.com \
--cc=daniel.lezcano@linaro.org \
--cc=edubezval@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=srikars@nvidia.com \
--cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).