From: Lukasz Luba <lukasz.luba@arm.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: linux-kernel@vger.kernel.org, cristian.marussi@arm.com,
rjw@rjwysocki.net, viresh.kumar@linaro.org,
nicola.mazzucato@arm.com, linux-arm-kernel@lists.infradead.org,
linux-pm@vger.kernel.org
Subject: Re: [PATCH v2] cpufreq: arm_scmi: Fix error path when allocation failed
Date: Wed, 4 Aug 2021 11:51:02 +0100 [thread overview]
Message-ID: <34c0a16b-4f82-8c78-9e29-63d462ea68b8@arm.com> (raw)
In-Reply-To: <20210803224145.zyr36sliwa7a67xf@bogus>
On 8/3/21 11:41 PM, Sudeep Holla wrote:
> On Tue, Aug 03, 2021 at 10:07:44AM +0100, Lukasz Luba wrote:
>> Stop the initialization when cpumask allocation failed and return an
>> error.
>>
>
> Good catch!
>
> Reviewed-by: Sudeep Holla <sudeep.holla@arm.com>
>
Thank you for the review!
WARNING: multiple messages have this Message-ID (diff)
From: Lukasz Luba <lukasz.luba@arm.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: linux-kernel@vger.kernel.org, cristian.marussi@arm.com,
rjw@rjwysocki.net, viresh.kumar@linaro.org,
nicola.mazzucato@arm.com, linux-arm-kernel@lists.infradead.org,
linux-pm@vger.kernel.org
Subject: Re: [PATCH v2] cpufreq: arm_scmi: Fix error path when allocation failed
Date: Wed, 4 Aug 2021 11:51:02 +0100 [thread overview]
Message-ID: <34c0a16b-4f82-8c78-9e29-63d462ea68b8@arm.com> (raw)
In-Reply-To: <20210803224145.zyr36sliwa7a67xf@bogus>
On 8/3/21 11:41 PM, Sudeep Holla wrote:
> On Tue, Aug 03, 2021 at 10:07:44AM +0100, Lukasz Luba wrote:
>> Stop the initialization when cpumask allocation failed and return an
>> error.
>>
>
> Good catch!
>
> Reviewed-by: Sudeep Holla <sudeep.holla@arm.com>
>
Thank you for the review!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-08-04 10:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 9:07 [PATCH v2] cpufreq: arm_scmi: Fix error path when allocation failed Lukasz Luba
2021-08-03 9:07 ` Lukasz Luba
2021-08-03 22:41 ` Sudeep Holla
2021-08-03 22:41 ` Sudeep Holla
2021-08-04 10:51 ` Lukasz Luba [this message]
2021-08-04 10:51 ` Lukasz Luba
2021-08-04 4:02 ` Viresh Kumar
2021-08-04 4:02 ` Viresh Kumar
2021-08-04 10:51 ` Lukasz Luba
2021-08-04 10:51 ` Lukasz Luba
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=34c0a16b-4f82-8c78-9e29-63d462ea68b8@arm.com \
--to=lukasz.luba@arm.com \
--cc=cristian.marussi@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nicola.mazzucato@arm.com \
--cc=rjw@rjwysocki.net \
--cc=sudeep.holla@arm.com \
--cc=viresh.kumar@linaro.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.