From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org,
Anup Sharma <anupnewsmail@gmail.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v2 1/2] perf build: Update build rule for generated files
Date: Wed, 9 Aug 2023 10:28:15 -0300 [thread overview]
Message-ID: <ZNOUb1Q5ifyLju/q@kernel.org> (raw)
In-Reply-To: <CAM9d7cgqJatFn0tQVOxoQymFUruSzniPi5Okb1sotb6VLt+X_g@mail.gmail.com>
Em Wed, Aug 09, 2023 at 03:56:17PM +0900, Namhyung Kim escreveu:
> On Fri, Jul 28, 2023 at 11:09 PM Arnaldo Carvalho de Melo <acme@kernel.org> wrote:
> > Em Thu, Jul 27, 2023 at 07:24:46PM -0700, Namhyung Kim escreveu:
> > > Let's update the build rule to specify those cases explicitly to depend
> > > on the files in the output directory.
> > > Note that it's not a complete fix and it needs the next patch for the
> > > include path too.
> > Applied, testing it on the container builds.
> I don't see these commits in the perf-tools{,-next} yet.
6 days perf build: Include generated header files properly Namhyung Kim 5 -9/+9
6 days perf build: Update build rule for generated files Namhyung Kim 2 -0/+16
https://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools-next.git/commit/?h=perf-tools-next&id=7822a8913f4c51c7d1aff793b525d60c3384fb5b
https://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools-next.git/commit/?h=perf-tools-next&id=c7e97f215a4ad634b746804679f5937d25f77e29
Did I miss something?
- Arnaldo
next prev parent reply other threads:[~2023-08-09 13:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 2:24 [PATCH v2 1/2] perf build: Update build rule for generated files Namhyung Kim
2023-07-28 2:24 ` [PATCH v2 2/2] perf build: Include generated header files properly Namhyung Kim
2023-07-28 14:09 ` [PATCH v2 1/2] perf build: Update build rule for generated files Arnaldo Carvalho de Melo
2023-08-09 6:56 ` Namhyung Kim
2023-08-09 13:28 ` Arnaldo Carvalho de Melo [this message]
2023-08-10 2:01 ` Namhyung Kim
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=ZNOUb1Q5ifyLju/q@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=anupnewsmail@gmail.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=stable@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox