From: Namhyung Kim <namhyung@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@kernel.org>,
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
Subject: Re: [PATCH] perf test: Fix a compile error on pe-file-parsing.c
Date: Tue, 27 Jun 2023 12:34:37 -0700 [thread overview]
Message-ID: <CAM9d7chvc7qVMN3N19avpy+noAkff=VaZiqio6Ozi1DM2+HdCw@mail.gmail.com> (raw)
In-Reply-To: <CAP-5=fVGjsDEFfCXzqsDEz_dnXm635qGTLD+7L9w2qhKNr5VNA@mail.gmail.com>
On Tue, Jun 27, 2023 at 7:56 AM Ian Rogers <irogers@google.com> wrote:
>
> On Mon, Jun 26, 2023 at 11:33 PM Namhyung Kim <namhyung@kernel.org> wrote:
> >
> > The dso__find_symbol_by_name() should be have idx pointer argument.
> > Found during the build-test.
> >
> > $ make build-test
> > ...
> > CC /tmp/tmp.6JwPK1xbWG/tests/pe-file-parsing.o
> > tests/pe-file-parsing.c: In function ‘run_dir’:
> > tests/pe-file-parsing.c:64:15: error: too few arguments to function ‘dso__find_symbol_by_name’
> > 64 | sym = dso__find_symbol_by_name(dso, "main");
> > | ^~~~~~~~~~~~~~~~~~~~~~~~
> > In file included from tests/pe-file-parsing.c:16:
> > /usr/local/google/home/namhyung/project/linux/tools/perf/util/symbol.h:135:16: note: declared here
> > 135 | struct symbol *dso__find_symbol_by_name(struct dso *dso, const char *name, size_t *idx);
> > | ^~~~~~~~~~~~~~~~~~~~~~~~
> >
> > Fixes: 259dce914e93 ("perf symbol: Remove symbol_name_rb_node")
> > Signed-off-by: Namhyung Kim <namhyung@kernel.org>
>
> Acked-by: Ian Rogers <irogers@google.com>
Applied to perf-tools-next, thanks!
prev parent reply other threads:[~2023-06-27 19:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 6:32 [PATCH] perf test: Fix a compile error on pe-file-parsing.c Namhyung Kim
2023-06-27 14:56 ` Ian Rogers
2023-06-27 19:34 ` Namhyung Kim [this message]
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='CAM9d7chvc7qVMN3N19avpy+noAkff=VaZiqio6Ozi1DM2+HdCw@mail.gmail.com' \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.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=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).