From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: Thomas Monjalon <thomas@monjalon.net>,
"zhaoyan.chen@intel.com" <zhaoyan.chen@intel.com>,
"ci@dpdk.org" <ci@dpdk.org>
Cc: "sys_stv@intel.com" <sys_stv@intel.com>,
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: Tue, 31 Mar 2020 20:12:31 +0000 [thread overview]
Message-ID: <BYAPR18MB2424E42AFC2CA01519C5636DC8C80@BYAPR18MB2424.namprd18.prod.outlook.com> (raw)
In-Reply-To: <1710734.dTVjPilprF@xps>
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Wednesday, April 1, 2020 1:33 AM
> To: zhaoyan.chen@intel.com; ci@dpdk.org; Jerin Jacob Kollanukkaran
> <jerinj@marvell.com>
> Cc: sys_stv@intel.com; Nithin Kumar Dabilpuram
> <ndabilpuram@marvell.com>; david.marchand@redhat.com
> Subject: [EXT] Re: Wrong Checkpatch failure in Intel CI
>
> External Email
>
> ----------------------------------------------------------------------
> 31/03/2020 21:51, Jerin Jacob Kollanukkaran:
> > Hello,
> >
> > It looks like "devtools/check-symbol-change.sh" cached in Intel Patchwork CI.
> > The commit[2] is fixed the issue reported by [1]. The commit[2]
> > already part of Master but some reason some this cached in CI system and it
> pick OLD checkpatch infra.
> >
> > Could someone look into this issue from Intel side?
> >
> >
> > [1]
> > https://urldefense.proofpoint.com/v2/url?u=http-3A__mails.dpdk.org_arc
> > hives_test-2Dreport_2020-
> 2DMarch_123095.html&d=DwICAg&c=nKjWec2b6R0mOy
> >
> Paz7xtfQ&r=1DGob4H4rxz6H8uITozGOCa0s5f4wCNtTa4UUKvcsvI&m=RErROLH
> hI94iK
> > fA-Ee95iCZBQDqP8JFGsyTT9Nq5e8w&s=iL1-
> HL1ttarMJ5bCAL0aIxUjp49eoa3xUMldw
> > ma-CTw&e=
>
> This email comes from checkpatch@dpdk.org This is not Intel infrastructure.
OK. I was not aware of it. Sorry guys.
> 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.
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.
>
> Side note: Marvell is allowed to run some tests and send reports as part of the
> distributed CI.
Good info.
>
next prev parent reply other threads:[~2020-03-31 20:12 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 ` Jerin Jacob Kollanukkaran [this message]
2020-03-31 20:39 ` [dpdk-ci] [EXT] " Thomas Monjalon
2020-04-01 11:22 ` Jerin Jacob Kollanukkaran
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=BYAPR18MB2424E42AFC2CA01519C5636DC8C80@BYAPR18MB2424.namprd18.prod.outlook.com \
--to=jerinj@marvell.com \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--cc=ndabilpuram@marvell.com \
--cc=sys_stv@intel.com \
--cc=thomas@monjalon.net \
--cc=zhaoyan.chen@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).