DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
	Andrew Rybchenko <arybchenko@solarflare.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Solarflare PMD submission question
Date: Mon, 21 Nov 2016 10:30:39 +0000	[thread overview]
Message-ID: <f0a999ba-6170-816a-7a5f-1763bc1179e8@intel.com> (raw)
In-Reply-To: <2553236.UbBGAtvXhx@xps13>

On 11/21/2016 8:59 AM, Thomas Monjalon wrote:
> 2016-11-21 11:46, Andrew Rybchenko:
>> On 11/21/2016 11:19 AM, Thomas Monjalon wrote:
>>>> Before submitting 56 patches I'd like to double-check that checkpatch.pl
>>>> errors (for example, because of assignments in the 'if' condition,
>>>> parenthesis around return value) is not a show-stopper for base driver
>>>> import.
>>> You can run checkpatches.sh or send the patches to checkpatch@dpdk.org.
>>> The script check-git-log.sh can also guide you for the expected formatting.
>>
>> Yes, I did it and it helped me to find and fix some coding standard 
>> violations.
>>
>> The problem with libefx (base driver) is that it is existing code which 
>> follows FreeBSD and illumos coding conventions which contradict to 
>> checkpatches.sh sometimes (e.g. require parenthesis around return 
>> value). Other example of error produced by checkpatches.sh is assign in 
>> if. It is widely used in the code to assign return code value and 
>> compare it vs 0 in one line. It is not a coding standard conflict, but 
>> it is very wide-spread in the code (so changing it will produce too many 
>> changes not strictly required/useful).
>>
>> So, may I repeat my question if it is a show-stopper for base driver or 
>> acceptable.
> 
> I would vote to accept these minor style warnings for the base driver.
> Ferruh, any comment?
> 

For _base driver_, I am also OK for having checkpatch warnings.

  reply	other threads:[~2016-11-21 10:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-27  6:34 Andrew Rybchenko
2016-10-27 10:37 ` Thomas Monjalon
2016-10-28 10:50   ` Andrew Rybchenko
2016-10-28 12:33     ` Thomas Monjalon
2016-10-28 13:05       ` Andrew Rybchenko
2016-10-28 13:14         ` Thomas Monjalon
2016-10-28 14:43       ` Andrew Rybchenko
2016-11-18 16:50         ` Andrew Rybchenko
2016-11-21  8:19           ` Thomas Monjalon
2016-11-21  8:46             ` Andrew Rybchenko
2016-11-21  8:59               ` Thomas Monjalon
2016-11-21 10:30                 ` Ferruh Yigit [this message]
2016-11-21 15:03                   ` Andrew Rybchenko

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=f0a999ba-6170-816a-7a5f-1763bc1179e8@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=arybchenko@solarflare.com \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@6wind.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).