From: Reinette Chatre <reinette.chatre@intel.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Muhammad Usama Anjum" <usama.anjum@collabora.com>,
"Shuah Khan" <shuah@kernel.org>,
linux-kselftest@vger.kernel.org
Cc: <linux-kernel@vger.kernel.org>,
Shaopeng Tan <tan.shaopeng@jp.fujitsu.com>,
Fenghua Yu <fenghua.yu@intel.com>
Subject: Re: [PATCH v2 2/3] selftests/resctrl: Always initialize ecx to avoid build warnings
Date: Thu, 22 Aug 2024 09:26:30 -0700 [thread overview]
Message-ID: <c569956b-a0c8-45fe-b51a-92d088407cfd@intel.com> (raw)
In-Reply-To: <20240822081114.4695-3-ilpo.jarvinen@linux.intel.com>
Hi Ilpo,
On 8/22/24 1:11 AM, Ilpo Järvinen wrote:
> To avoid warnings when __cpuid_count() is an empty stub, always
> initialize ecx because it is used in the return statement.
>
> Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
> Reviewed-by: Muhammad Usama Anjum <usama.anjum@collabora.com>
> ---
Acked-by: Reinette Chatre <reinette.chatre@intel.com>
Reinette
next prev parent reply other threads:[~2024-08-22 16:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 8:11 [PATCH v2 0/3] selftests: Fix cpuid / vendor checking build issues Ilpo Järvinen
2024-08-22 8:11 ` [PATCH v2 1/3] selftests/resctrl: Generalize non-contiguous CAT check Ilpo Järvinen
2024-08-22 16:26 ` Reinette Chatre
2024-08-22 8:11 ` [PATCH v2 2/3] selftests/resctrl: Always initialize ecx to avoid build warnings Ilpo Järvinen
2024-08-22 16:26 ` Reinette Chatre [this message]
2024-08-22 8:11 ` [PATCH v2 3/3] kselftest: Provide __cpuid_count() stub on non-x86 archs Ilpo Järvinen
2024-08-22 16:27 ` Reinette Chatre
2024-08-23 10:47 ` Ilpo Järvinen
2024-08-23 16:17 ` Reinette Chatre
2024-08-26 10:44 ` Ilpo Järvinen
2024-08-26 15:33 ` Reinette Chatre
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=c569956b-a0c8-45fe-b51a-92d088407cfd@intel.com \
--to=reinette.chatre@intel.com \
--cc=fenghua.yu@intel.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=tan.shaopeng@jp.fujitsu.com \
--cc=usama.anjum@collabora.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