From: Tom Rini <trini@konsulko.com>
To: Simon Glass <sjg@chromium.org>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
Love Kumar <love.kumar@amd.com>
Subject: Re: [PATCH 4/4] test: Make net tests depend on CONFIG_CMD_NET
Date: Sat, 25 Jan 2025 16:50:42 -0600 [thread overview]
Message-ID: <20250125225042.GH60249@bill-the-cat> (raw)
In-Reply-To: <CAFLszTiqhKn4DF0CQg7egocvvVTu_NhC4BgGaOV6j8zbDXkoxw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1434 bytes --]
On Sat, Jan 25, 2025 at 03:47:26PM -0700, Simon Glass wrote:
> Hi Tom,
>
> On Sat, 25 Jan 2025 at 14:44, Tom Rini <trini@konsulko.com> wrote:
> >
> > On Sat, Jan 25, 2025 at 02:31:39PM -0700, Simon Glass wrote:
> > > This fails on samus_tpl as there is no 'net' command.
> > >
> > > => net list
> > > Unknown command 'net' - try 'help' !
> > >
> > > Fix it by adding a condition for the test.
> >
> > For this part,
> > Reviewed-by: Tom Rini <trini@konsulko.com>
> >
> > > Add a blank line to keep pylint happy.
> >
> > Can we silence that pylint? I don't look forward to the churn of adding
> > more blanks everywhere especially since imo it doesn't improve
> > readability either.
>
> Yes, but we would want to do it globally. But it isn't really a good
> idea IMO. We are trying to use PEP8 which loads of tools expect...e.g.
> my IDE shows warnings in this case. It might be better to just fix the
> problems.
>
> As to readability, I'm on the fence...in practice it doesn't matter
> much as few non-trivial programs have a lot of top-level functions. I
> would rather keep the tool happy and use the Python style that people
> expect when coming into the project.
Yes, we should do it globally. Can we not globally also tell tools the
deviations from PEP8? I remember back when people would argue about if
we should tell file editors what to expect for whitespace, etc :)
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2025-01-25 22:50 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-25 21:31 [PATCH 0/4] test: A few quality-of-life improvements Simon Glass
2025-01-25 21:31 ` Simon Glass
2025-01-25 21:31 ` [PATCH 1/4] test/py: Shorten u_boot_console Simon Glass
2025-01-25 21:50 ` Tom Rini
2025-01-25 21:50 ` Tom Rini
2025-01-25 22:42 ` Simon Glass
2025-01-25 22:42 ` Simon Glass
2025-01-25 22:55 ` Tom Rini
2025-01-25 22:55 ` Tom Rini
2025-01-25 22:58 ` Simon Glass
2025-01-25 22:58 ` Simon Glass
2025-02-03 6:04 ` Love Kumar via Linux-erofs
2025-02-03 6:04 ` Love Kumar
2025-02-09 14:29 ` Simon Glass
2025-02-09 14:29 ` Simon Glass
2025-01-25 21:31 ` [PATCH 2/4] test: Drop u_boot_ prefix on test files Simon Glass
2025-01-25 21:46 ` Tom Rini
2025-01-25 22:41 ` Simon Glass
2025-01-25 22:57 ` Tom Rini
2025-01-25 22:59 ` Simon Glass
2025-01-25 21:31 ` [PATCH 3/4] test/py: Show info about module-loading Simon Glass
2025-01-25 21:43 ` Tom Rini
2025-01-25 23:00 ` Simon Glass
2025-01-25 23:02 ` Tom Rini
2025-01-25 23:39 ` Simon Glass
2025-01-25 23:53 ` Tom Rini
2025-01-25 21:31 ` [PATCH 4/4] test: Make net tests depend on CONFIG_CMD_NET Simon Glass
2025-01-25 21:44 ` Tom Rini
2025-01-25 22:47 ` Simon Glass
2025-01-25 22:50 ` Tom Rini [this message]
2025-01-25 22:56 ` Simon Glass
2025-01-25 23:00 ` Tom Rini
2025-02-15 13:02 ` Simon Glass
2025-02-15 14:37 ` Tom Rini
2025-02-15 17:21 ` 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=20250125225042.GH60249@bill-the-cat \
--to=trini@konsulko.com \
--cc=love.kumar@amd.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
/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.