From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "ci@dpdk.org" <ci@dpdk.org>,
Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>,
"david.marchand@redhat.com" <david.marchand@redhat.com>
Subject: Re: [dpdk-ci] [EXT] Re: Wrong Checkpatch failure in Intel CI
Date: Wed, 1 Apr 2020 11:22:50 +0000 [thread overview]
Message-ID: <BYAPR18MB24240B4BEBE87ED2A91683E3C8C90@BYAPR18MB2424.namprd18.prod.outlook.com> (raw)
In-Reply-To: <13671738.mzqWEpnEhh@xps>
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Wednesday, April 1, 2020 2:09 AM
> To: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
> Cc: ci@dpdk.org; Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>;
> david.marchand@redhat.com
> Subject: Re: [EXT] Re: Wrong Checkpatch failure in Intel CI
>
> 31/03/2020 22:12, Jerin Jacob Kollanukkaran:
> > > From: Thomas Monjalon <thomas@monjalon.net> I will update checkpatch
> > > on dpdk.org.
> >
> > The actual change is in devtools/check-symbol-change.sh. I am not sure why it
> is not picking up.
>
> This is because the scripts used by checkpatch@dpdk.org are not updated
> automatically.
> Why not? Because I never took time for it.
>
> > Hope updating the checkpatch will fix it.
> > Just for the record, I am testing with checkpatch.pl from 5.6.0-rc5 kernel +
> todays dpdk.org master.
>
> Tell me if you still see an issue.
I assume, I can NOT verify now by re-trigger or something.
I will report this issue if it is comes up in future in any of my patch.
>
next prev parent reply other threads:[~2020-04-01 11:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 19:51 [dpdk-ci] " Jerin Jacob Kollanukkaran
2020-03-31 20:03 ` Thomas Monjalon
2020-03-31 20:12 ` [dpdk-ci] [EXT] " Jerin Jacob Kollanukkaran
2020-03-31 20:39 ` Thomas Monjalon
2020-04-01 11:22 ` Jerin Jacob Kollanukkaran [this message]
2020-04-01 12:18 ` 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=BYAPR18MB24240B4BEBE87ED2A91683E3C8C90@BYAPR18MB2424.namprd18.prod.outlook.com \
--to=jerinj@marvell.com \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--cc=ndabilpuram@marvell.com \
--cc=thomas@monjalon.net \
/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).