From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Leo Yan <leo.yan@arm.com>
Cc: Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@linaro.org>,
Alice Rogers <alice.mei.rogers@gmail.com>,
Aishwarya TCV <aishwarya.tcv@arm.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] perf python: Fix pylint warnings without Textual
Date: Wed, 4 Nov 2026 18:16:31 -0300 [thread overview]
Message-ID: <auugr4_wlpdtaSy2@phoenix2> (raw)
In-Reply-To: <20261023-perf_fix_pylint_warning-v1-0-b9da8dae2fe9@arm.com>
On Fri, Oct 23, 2026 at 02:20:23PM +0100, Leo Yan wrote:
> An arm64 cross build without Textual on the host reports W0201 warnings
> in treport.py and ttimechart.py, causing the build to fail.
>
> Initialize the inherited attributes in their constructors so pylint can
> recognize them without resolving the Textual base classes.
Seems simple enough, applying for v7.4.
- Arnaldo
> Signed-off-by: Leo Yan <leo.yan@arm.com>
> ---
> Leo Yan (2):
> perf treport: Initialize the subtitle in the constructor
> perf timechart: Initialize Textual attributes in constructors
>
> tools/perf/python/treport.py | 2 +-
> tools/perf/python/ttimechart.py | 2 ++
> 2 files changed, 3 insertions(+), 1 deletion(-)
> ---
> base-commit: 1c90f0a3c8a1c4e38f9edd97af9e20848805a7fb
> change-id: 20261023-perf_fix_pylint_warning-58408f0b6c91
>
> Best regards,
> --
> Leo Yan <leo.yan@arm.com>
>
prev parent reply other threads:[~2026-11-04 21:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 13:20 Leo Yan
2026-10-23 13:20 ` [PATCH 1/2] perf treport: Initialize the subtitle in the constructor Leo Yan
2026-10-23 13:20 ` [PATCH 2/2] perf timechart: Initialize Textual attributes in constructors Leo Yan
2026-11-04 21:16 ` Arnaldo Carvalho de Melo [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=auugr4_wlpdtaSy2@phoenix2 \
--to=acme@kernel.org \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=aishwarya.tcv@arm.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=alice.mei.rogers@gmail.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=leo.yan@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=namhyung@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
all inboxes | Powered by JetHome®