From: David Marchand <david.marchand@redhat.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Robin Jarry <rjarry@redhat.com>,
dev@dpdk.org, Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Subject: Re: [PATCH] dpdk-pmdinfo: remove unneeded whitespace
Date: Tue, 9 Jul 2024 06:49:28 +0200 [thread overview]
Message-ID: <CAJFAV8xLEuuUQa17i2AdpFLqgp5sy5-3Z=cK2ito1=4gie7Wpg@mail.gmail.com> (raw)
In-Reply-To: <D2F1B255LXIG.1JGJDIWI79J10@redhat.com>
On Tue, Jul 2, 2024 at 1:59 PM Robin Jarry <rjarry@redhat.com> wrote:
>
> Stephen Hemminger, Jul 01, 2024 at 19:58:
> > Fix the warning
> > $ flake8 --max-line-length=100 dpdk-pmdinfo.py
> > dpdk-pmdinfo.py:217:40: E203 whitespace before ':'
> >
> > Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> Acked-by: Robin Jarry <rjarry@redhat.com>
Applied, thanks.
--
David Marchand
prev parent reply other threads:[~2024-07-09 4:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 17:58 Stephen Hemminger
2024-07-02 11:59 ` Robin Jarry
2024-07-09 4:49 ` David Marchand [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='CAJFAV8xLEuuUQa17i2AdpFLqgp5sy5-3Z=cK2ito1=4gie7Wpg@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=rjarry@redhat.com \
--cc=stephen@networkplumber.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).