From: Thomas Monjalon <thomas@monjalon.net>
To: luca.boccassi@gmail.com
Cc: dev@dpdk.org, ferruh.yigit@intel.com, david.marchand@redhat.com,
akhil.goyal@nxp.com
Subject: Re: [dpdk-dev] [PATCH] Fix spelling errors that Lintian complains about
Date: Wed, 04 Nov 2020 19:34:50 +0100 [thread overview]
Message-ID: <1688321.1kAK0QkY3B@thomas> (raw)
In-Reply-To: <20201029133633.3733075-1-luca.boccassi@gmail.com>
29/10/2020 14:36, luca.boccassi@gmail.com:
> From: Luca Boccassi <luca.boccassi@microsoft.com>
>
> Signed-off-by: Luca Boccassi <luca.boccassi@microsoft.com>
> ---
> Would be really great to hook up some spell checkers to the CI, so
> that I'm not the only one who gets nagged by automated tools :-)
There is a spell checker with checkpatch
and we are catching/fixing some of them while merging.
Applied, thank you for fixing more.
next prev parent reply other threads:[~2020-11-04 18:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 13:36 luca.boccassi
2020-11-04 18:34 ` Thomas Monjalon [this message]
2020-11-04 19:10 ` Thomas Monjalon
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=1688321.1kAK0QkY3B@thomas \
--to=thomas@monjalon.net \
--cc=akhil.goyal@nxp.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=luca.boccassi@gmail.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;
as well as URLs for NNTP newsgroup(s).