* [dpdk-dev] checkpatch script
@ 2014-11-25 13:11 De Lara Guarch, Pablo
2014-11-25 14:28 ` Thomas Monjalon
0 siblings, 1 reply; 3+ messages in thread
From: De Lara Guarch, Pablo @ 2014-11-25 13:11 UTC (permalink / raw)
To: dev
Hi Thomas,
As we have seen the issues we have had on previous patches due to checkpatch, would it be possible to include the up-to-date script in the repo? I have realized that people either do not check their patches or check them with an old version that do not catch some errors that the latest one does, so I think this is a problem.
Plus, I think it would be a good idea to mention it in dpdk.org/dev, as this is clearly a requirement for merging patches.
Thanks,
Pablo
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [dpdk-dev] checkpatch script
2014-11-25 13:11 [dpdk-dev] checkpatch script De Lara Guarch, Pablo
@ 2014-11-25 14:28 ` Thomas Monjalon
2014-11-25 14:48 ` De Lara Guarch, Pablo
0 siblings, 1 reply; 3+ messages in thread
From: Thomas Monjalon @ 2014-11-25 14:28 UTC (permalink / raw)
To: De Lara Guarch, Pablo; +Cc: dev
Hi Pablo,
2014-11-25 13:11, De Lara Guarch, Pablo:
> Hi Thomas,
>
> As we have seen the issues we have had on previous patches due to
> checkpatch,
No we have no issues because of checkpatch ;)
It helps us to see some obvious errors.
> would it be possible to include the up-to-date script in the
> repo? I have realized that people either do not check their patches or check
> them with an old version that do not catch some errors that the latest one
> does, so I think this is a problem.
The real problem is to clearly define all the coding rules and adapt
checkpatch to our needs.
> Plus, I think it would be a good idea to mention it in dpdk.org/dev, as this
> is clearly a requirement for merging patches.
Please, let's close DPDK 1.8 first.
Then we'll have to write some documents and tools to make them approved
after necessary discussions/debates.
--
Thomas
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [dpdk-dev] checkpatch script
2014-11-25 14:28 ` Thomas Monjalon
@ 2014-11-25 14:48 ` De Lara Guarch, Pablo
0 siblings, 0 replies; 3+ messages in thread
From: De Lara Guarch, Pablo @ 2014-11-25 14:48 UTC (permalink / raw)
To: Thomas Monjalon; +Cc: dev
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Tuesday, November 25, 2014 2:29 PM
> To: De Lara Guarch, Pablo
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] checkpatch script
>
> Hi Pablo,
>
> 2014-11-25 13:11, De Lara Guarch, Pablo:
> > Hi Thomas,
> >
> > As we have seen the issues we have had on previous patches due to
> > checkpatch,
>
> No we have no issues because of checkpatch ;)
> It helps us to see some obvious errors.
I agree. With issues, I meant just confusion between using one version of checkpatch or another
(mind that you are using script from 3.18-rc6, the very latest one), so it was good that you mentioned the version before :)
>
> > would it be possible to include the up-to-date script in the
> > repo? I have realized that people either do not check their patches or check
> > them with an old version that do not catch some errors that the latest one
> > does, so I think this is a problem.
>
> The real problem is to clearly define all the coding rules and adapt
> checkpatch to our needs.
Agree 100%.
>
> > Plus, I think it would be a good idea to mention it in dpdk.org/dev, as this
> > is clearly a requirement for merging patches.
>
> Please, let's close DPDK 1.8 first.
> Then we'll have to write some documents and tools to make them approved
> after necessary discussions/debates.
OK. We will discuss it for 2.0. Thanks Thomas!
>
> --
> Thomas
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2014-11-25 14:40 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-11-25 13:11 [dpdk-dev] checkpatch script De Lara Guarch, Pablo
2014-11-25 14:28 ` Thomas Monjalon
2014-11-25 14:48 ` De Lara Guarch, Pablo
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).