From: Florian Fainelli <f.fainelli@gmail.com>
To: Khem Raj <raj.khem@gmail.com>, linux-perf-users@vger.kernel.org
Cc: Adrian Hunter <adrian.hunter@intel.com>,
Fangrui Song <maskray@google.com>,
Ian Rogers <irogers@google.com>, Jiri Olsa <jolsa@kernel.org>,
John Keeping <john@metanate.com>, Leo Yan <leo.yan@linaro.org>,
Michael Petlan <mpetlan@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Sedat Dilek <sedat.dilek@gmail.com>
Subject: Re: [PATCH] perf python: Account for multiple words in CC
Date: Mon, 5 Dec 2022 13:01:10 -0800 [thread overview]
Message-ID: <7d262374-1217-d79a-ff2d-d6626a98e195@gmail.com> (raw)
In-Reply-To: <20221205025534.150006-1-raj.khem@gmail.com>
On 12/4/22 18:55, Khem Raj wrote:
> Sometimes build systems may append options e.g. --sysroot etc. to CC
> variable especially in cross-compile environments like yocto project
> where CC varable is composed of cross-compiler name and some needed
> options for it to work in a relocatable environment. Therefore separate
> out the compiler name from rest of the options in CC, then add the
> options via second argument to Popen() API
>
> Cc: Adrian Hunter <adrian.hunter@intel.com>
> Cc: Fangrui Song <maskray@google.com>
> Cc: Florian Fainelli <f.fainelli@gmail.com>
> Cc: Ian Rogers <irogers@google.com>
> Cc: Jiri Olsa <jolsa@kernel.org>
> Cc: John Keeping <john@metanate.com>
> Cc: Leo Yan <leo.yan@linaro.org>
> Cc: Michael Petlan <mpetlan@redhat.com>
> Cc: Namhyung Kim <namhyung@kernel.org>
> Cc: Nathan Chancellor <nathan@kernel.org>
> Cc: Nick Desaulniers <ndesaulniers@google.com>
> Cc: Sedat Dilek <sedat.dilek@gmail.com>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
FWIW:
Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
--
Florian
next prev parent reply other threads:[~2022-12-05 21:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 2:55 [PATCH] perf python: Account for multiple words in CC Khem Raj
2022-12-05 21:01 ` Florian Fainelli [this message]
2022-12-12 18:53 ` Arnaldo Carvalho de Melo
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=7d262374-1217-d79a-ff2d-d6626a98e195@gmail.com \
--to=f.fainelli@gmail.com \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=john@metanate.com \
--cc=jolsa@kernel.org \
--cc=leo.yan@linaro.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=maskray@google.com \
--cc=mpetlan@redhat.com \
--cc=namhyung@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=raj.khem@gmail.com \
--cc=sedat.dilek@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).