From: Shuah Khan <skhan@linuxfoundation.org>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>,
Thomas Renninger <trenn@suse.com>, Shuah Khan <shuah@kernel.org>,
"John B. Wyatt IV" <jwyatt@redhat.com>,
John Kacur <jkacur@redhat.com>,
"open list:CPU POWER MONITORING SUBSYSTEM"
<linux-pm@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Cc: Peng Fan <peng.fan@nxp.com>, Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH 2/2] pm: cpupower: Makefile: better support cross-compiling
Date: Thu, 12 Sep 2024 09:21:22 -0600 [thread overview]
Message-ID: <0f8df90f-007a-483e-83ce-df8ff0e99791@linuxfoundation.org> (raw)
In-Reply-To: <20240912013846.3058728-2-peng.fan@oss.nxp.com>
On 9/11/24 19:38, Peng Fan (OSS) wrote:
> From: Peng Fan <peng.fan@nxp.com>
Improve subject line. "better support cross-compiling" doesn't
tell me much. "Allow overriding cross-compiling env params" would
is a better subject line for this patch.
>
> Allow overridding the envs, this will be easier to user Yocto
"Allow overriding the cross-comple env parameters to make it
easier for Yactor users."
Then add what it is like now and how this change helps.
spelling "overridding"?. Run checkpatch on patches before sending.
> cross-compiler toolchains to build cpupower with only two steps:
>
> source (toolchain path)/environment-setup-armv8a-poky-linux
> make
>
What steps do you have to take without this change? Include that
in the changelog
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---
> tools/power/cpupower/Makefile | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/tools/power/cpupower/Makefile b/tools/power/cpupower/Makefile
> index 6c02f401069e..e2a48af6fa2a 100644
> --- a/tools/power/cpupower/Makefile
> +++ b/tools/power/cpupower/Makefile
> @@ -86,12 +86,12 @@ INSTALL_SCRIPT = ${INSTALL} -m 644
> # If you are running a cross compiler, you may want to set this
> # to something more interesting, like "arm-linux-". If you want
> # to compile vs uClibc, that can be done here as well.
> -CROSS = #/usr/i386-linux-uclibc/usr/bin/i386-uclibc-
> -CC = $(CROSS)gcc
> -LD = $(CROSS)gcc
> -AR = $(CROSS)ar
> -STRIP = $(CROSS)strip
> -RANLIB = $(CROSS)ranlib
> +CROSS ?= #/usr/i386-linux-uclibc/usr/bin/i386-uclibc-
> +CC ?= $(CROSS)gcc
> +LD ?= $(CROSS)gcc
> +AR ?= $(CROSS)ar
> +STRIP ?= $(CROSS)strip
> +RANLIB ?= $(CROSS)ranlib
> HOSTCC = gcc
> MKDIR = mkdir
>
Send v2 with cover-letter to make easier for reviewers.
thanks,
-- Shuah
next prev parent reply other threads:[~2024-09-12 15:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 1:38 [PATCH 1/2] pm: cpupower: bench: print path fopen failed Peng Fan (OSS)
2024-09-12 1:38 ` [PATCH 2/2] pm: cpupower: Makefile: better support cross-compiling Peng Fan (OSS)
2024-09-12 15:21 ` Shuah Khan [this message]
2024-09-12 12:28 ` [PATCH 1/2] pm: cpupower: bench: print path fopen failed John B. Wyatt IV
2024-09-12 12:31 ` Peng Fan
2024-09-12 15:15 ` Shuah Khan
2024-09-17 12:37 ` Peng Fan
2024-09-19 16:08 ` Shuah Khan
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=0f8df90f-007a-483e-83ce-df8ff0e99791@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=jkacur@redhat.com \
--cc=jwyatt@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--cc=shuah@kernel.org \
--cc=trenn@suse.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®