From: Namhyung Kim <namhyung@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
James Clark <james.clark@linaro.org>,
Charlie Jenkins <charlie@rivosinc.com>,
John Garry <john.g.garry@oracle.com>,
Veronika Molnarova <vmolnaro@redhat.com>,
"Masami Hiramatsu (Google)" <mhiramat@kernel.org>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Ian Rogers <irogers@google.com>
Subject: Re: [PATCH v2 0/6] Mypy and pylint build support
Date: Tue, 25 Mar 2025 12:49:30 -0700 [thread overview]
Message-ID: <174293217022.2401011.8796025370875674731.b4-ty@kernel.org> (raw)
In-Reply-To: <20250311213628.569562-1-irogers@google.com>
On Tue, 11 Mar 2025 14:36:22 -0700, Ian Rogers wrote:
> Support building perf checking the python code with mypy and/or
> pylint. Currently there are too many errors to make this a default.
>
> Shellcheck generates no output on success, so linking shellcheck files
> doesn't cause `ld` to fail. Mypy and pylint generate output that will
> break `ld` so change the Makefile.build to ignore test log files.
>
> [...]
Applied to perf-tools-next, thanks!
Best regards,
Namhyung
prev parent reply other threads:[~2025-03-25 19:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 21:36 Ian Rogers
2025-03-11 21:36 ` [PATCH v2 1/6] tools/build: Don't pass test log files to linker Ian Rogers
2025-03-11 21:36 ` [PATCH v2 2/6] perf build: Rename TEST_LOGS to SHELL_TEST_LOGS Ian Rogers
2025-03-11 21:36 ` [PATCH v2 3/6] perf build: Add mypy build tests Ian Rogers
2025-03-11 21:36 ` [PATCH v2 4/6] perf build: Add pylint " Ian Rogers
2025-03-11 21:36 ` [PATCH v2 5/6] perf test: Address attr.py mypy error Ian Rogers
2025-03-11 21:36 ` [PATCH v2 6/6] perf python: Fix setup.py mypy errors Ian Rogers
2025-03-24 16:15 ` [PATCH v2 0/6] Mypy and pylint build support Ian Rogers
2025-03-25 19:49 ` 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=174293217022.2401011.8796025370875674731.b4-ty@kernel.org \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=charlie@rivosinc.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=john.g.garry@oracle.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=vmolnaro@redhat.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®