From: Guenter Roeck <linux@roeck-us.net>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: Ed Brindley <kernel@maidavale.org>,
Denis Pauk <pauk.denis@gmail.com>,
Jean Delvare <jdelvare@suse.com>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-hwmon@vger.kernel.org
Subject: Re: [PATCH v2] hwmon: (asus_wmi_sensors) Save a few bytes of memory
Date: Sat, 2 Jul 2022 12:13:16 -0700 [thread overview]
Message-ID: <20220702191316.GA3131040@roeck-us.net> (raw)
In-Reply-To: <e23cea6c489fabb109a61e8a33d146a6b74c0529.1656741926.git.christophe.jaillet@wanadoo.fr>
On Sat, Jul 02, 2022 at 08:05:54AM +0200, Christophe JAILLET wrote:
> The first 'for' loop of asus_wmi_configure_sensor_setup() only computes
> the number and type of sensors that exist in the system.
>
> Here, the 'temp_sensor' structure is only used to store the data collected
> by asus_wmi_sensor_info(). There is no point in using a devm_ variant for
> this allocation. This wastes some memory for no good reason.
>
> Use the stack instead.
>
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Applied to hwmon-next.
Thanks,
Guenter
> ---
> v1 -> v2: Use the stack instead of kmalloc/kfree to simplify even more the
> code (Guenter Roeck)
> ---
> drivers/hwmon/asus_wmi_sensors.c | 12 +++++-------
> 1 file changed, 5 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/hwmon/asus_wmi_sensors.c b/drivers/hwmon/asus_wmi_sensors.c
> index 9e935e34c998..6e8a908171f0 100644
> --- a/drivers/hwmon/asus_wmi_sensors.c
> +++ b/drivers/hwmon/asus_wmi_sensors.c
> @@ -514,22 +514,20 @@ static int asus_wmi_configure_sensor_setup(struct device *dev,
> int i, idx;
> int err;
>
> - temp_sensor = devm_kcalloc(dev, 1, sizeof(*temp_sensor), GFP_KERNEL);
> - if (!temp_sensor)
> - return -ENOMEM;
> -
> for (i = 0; i < sensor_data->wmi.sensor_count; i++) {
> - err = asus_wmi_sensor_info(i, temp_sensor);
> + struct asus_wmi_sensor_info sensor;
> +
> + err = asus_wmi_sensor_info(i, &sensor);
> if (err)
> return err;
>
> - switch (temp_sensor->data_type) {
> + switch (sensor.data_type) {
> case TEMPERATURE_C:
> case VOLTAGE:
> case CURRENT:
> case FAN_RPM:
> case WATER_FLOW:
> - type = asus_data_types[temp_sensor->data_type];
> + type = asus_data_types[sensor.data_type];
> if (!nr_count[type])
> nr_types++;
> nr_count[type]++;
prev parent reply other threads:[~2022-07-02 19:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-02 6:05 Christophe JAILLET
2022-07-02 19:13 ` Guenter Roeck [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=20220702191316.GA3131040@roeck-us.net \
--to=linux@roeck-us.net \
--cc=christophe.jaillet@wanadoo.fr \
--cc=jdelvare@suse.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kernel@maidavale.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pauk.denis@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
all inboxes | Powered by JetHome®