From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Alejandro Lucero <alejandro.lucero@netronome.com>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] Fwd: |WARNING| [PATCH] nfp: report link speed using hardware info
Date: Fri, 18 Nov 2016 16:44:43 +0100 [thread overview]
Message-ID: <2349367.5psuzfVfT8@xps13> (raw)
In-Reply-To: <CAD+H992NtFefKXxNQiJng7i+6AtJywSSuLCaU4D-TBw_Svj17g@mail.gmail.com>
2016-11-18 15:31, Alejandro Lucero:
> On Fri, Nov 18, 2016 at 3:24 PM, Ferruh Yigit <ferruh.yigit@intel.com>
> wrote:
>
> > On 11/18/2016 3:10 PM, Alejandro Lucero wrote:
> > > Hi Thomas,
> > >
> > > I got this email when sending a patch some minutes ago.
> > >
> > > The point is I trusted script/checkpatches.sh which did not report those
> > > warnings.
> > > Am I doing anything wrong when using checkpatches.sh?
> >
> > I am also getting same warnings as below, this can be related to the
> > checkpatch.pl version.
> >
> > I have: Version: 0.32
> > (./scripts/checkpatch.pl --version)
> >
> Uhmm, I got same one.
The last update of this version number is from 2011...
I guess we have to live without checkpatch versioning.
next prev parent reply other threads:[~2016-11-18 15:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 15:04 [dpdk-dev] " Alejandro Lucero
[not found] ` <20161118150433.AD575558B@dpdk.org>
2016-11-18 15:10 ` [dpdk-dev] Fwd: |WARNING| " Alejandro Lucero
2016-11-18 15:24 ` Ferruh Yigit
2016-11-18 15:31 ` Alejandro Lucero
2016-11-18 15:42 ` Alejandro Lucero
2016-11-18 15:44 ` Thomas Monjalon [this message]
2016-11-18 15:34 ` Thomas Monjalon
2016-11-18 15:26 ` Ferruh Yigit
2016-11-18 15:33 ` Alejandro Lucero
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=2349367.5psuzfVfT8@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=alejandro.lucero@netronome.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.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).