From: Tom Rini <trini@konsulko.com>
To: Simon Glass <sjg@chromium.org>
Cc: "U-Boot Mailing List" <u-boot@lists.denx.de>,
"Heinrich Schuchardt" <xypron.glpk@gmx.de>,
"Marek Behún" <marek.behun@nic.cz>,
"Masahiro Yamada" <yamada.masahiro@socionext.com>,
"Pali Rohár" <pali@kernel.org>
Subject: Re: [PATCH 5/6] Makefile: Add a pylint checker to the build
Date: Tue, 25 Jan 2022 10:57:02 -0500 [thread overview]
Message-ID: <20220125155702.GN7515@bill-the-cat> (raw)
In-Reply-To: <20211122034841.304138-2-sjg@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 465 bytes --]
On Sun, Nov 21, 2021 at 08:48:40PM -0700, Simon Glass wrote:
> At present the Python code in U-Boot is somewhat inconsistent, with some
> files passing pylint quite cleanly and others not.
>
> Add a way to track progress on this clean-up, by checking that no module
> has got any worse as a result of changes.
>
> This can be used with 'make pylint'.
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
Applied to u-boot/master, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2022-01-25 15:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 3:48 [PATCH 0/6] Add a pylint check Simon Glass
2021-11-22 3:48 ` [PATCH 1/6] .gitignore: Ignore any html coverage directory Simon Glass
2022-01-25 15:56 ` Tom Rini
2021-11-22 3:48 ` [PATCH 2/6] dtoc: Fix up a code comment that confuses pylint Simon Glass
2021-11-22 6:45 ` Heinrich Schuchardt
2022-01-25 15:56 ` Tom Rini
2021-11-22 3:48 ` [PATCH 3/6] patman: Update the list of modules Simon Glass
2022-01-25 15:56 ` Tom Rini
2021-11-22 3:48 ` [PATCH 4/6] tools: Add init files for Python tools Simon Glass
2022-01-25 15:56 ` Tom Rini
2021-11-22 3:48 ` [PATCH 5/6] Makefile: Add a pylint checker to the build Simon Glass
2021-11-22 8:05 ` Heinrich Schuchardt
2021-11-25 0:13 ` Simon Glass
2022-01-25 15:56 ` Tom Rini
2022-01-25 15:57 ` Tom Rini [this message]
2021-11-22 3:48 ` [PATCH 6/6] Azure/GitLab CI: Add the pylint checker Simon Glass
2021-11-22 7:40 ` Heinrich Schuchardt
2021-11-25 0:13 ` Simon Glass
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=20220125155702.GN7515@bill-the-cat \
--to=trini@konsulko.com \
--cc=marek.behun@nic.cz \
--cc=pali@kernel.org \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
--cc=yamada.masahiro@socionext.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.