From: Bruce Richardson <bruce.richardson@intel.com>
To: "Jan Mędala" <jan@semihalf.com>
Cc: dev@dpdk.org, Alexander Matushevsky <matua@amazon.com>
Subject: Re: [dpdk-dev] [PATCH v5 0/4] DPDK polling-mode driver for Amazon Elastic Network Adapters (ENA)
Date: Thu, 10 Mar 2016 12:00:01 +0000 [thread overview]
Message-ID: <20160310120000.GF14712@bricha3-MOBL3> (raw)
In-Reply-To: <CANw_3ZcYptLH+PfBj_43-3mF8KhjpJPkW0Toay+_6ooTcPohJQ@mail.gmail.com>
On Wed, Mar 09, 2016 at 12:34:51PM +0100, Jan Mędala wrote:
> I'd like to kindly request for review and comments.
>
> Jan
Hi Jan,
I've run checkpatch on these patches and below is some of the output that you
might want to look at fixing. As well as these, there were a *lot* of warnings
about lines over 80 characters, and indeed over 90 characters (since we allow
a little bit of wiggle-room in line length, I checked with 90 too).
Regards,
/Bruce
Patch 1:
--------
ERROR:TRAILING_WHITESPACE: trailing whitespace
#200: FILE: doc/guides/nics/ena.rst:165:
+Any Linux distribution fulfilling the conditions described in ``System Requirements`` $
Patch 2:
--------
ERROR:INITIALISED_STATIC: do not initialise statics to 0
#83: FILE: drivers/net/ena/base/ena_com.c:68:
+static int ena_alloc_cnt = 0;
ERROR:ASSIGN_IN_IF: do not use assignment in if condition
#493: FILE: drivers/net/ena/base/ena_com.c:478:
+ if ((syst = ENA_GET_SYSTEM_USECS()) > timeout) {
CHECK:BRACES: Blank lines aren't necessary after an open brace '{'
#1818: FILE: drivers/net/ena/base/ena_com.c:1803:
+{
+
CHECK:LINE_SPACING: Please don't use multiple blank lines
#5574: FILE: drivers/net/ena/base/ena_defs/ena_admin_defs_custom.h:39:
+
+
ERROR:C99_COMMENTS: do not use C99 // comments
#5575: FILE: drivers/net/ena/base/ena_defs/ena_admin_defs_custom.h:40:
+#endif //_ENA_ADMIN_QUEUE_CUSTOM_H_
Patch 3:
--------
WARNING:NEW_TYPEDEFS: do not add new typedefs
#67: FILE: drivers/net/ena/base/ena_plat_dpdk.h:50:
+typedef rte_atomic32_t ena_atomic32_t;
WARNING:NEW_TYPEDEFS: do not add new typedefs
#75: FILE: drivers/net/ena/base/ena_plat_dpdk.h:58:
+typedef void *ena_mem_handle_t;
WARNING:NEW_TYPEDEFS: do not add new typedefs
#150: FILE: drivers/net/ena/base/ena_plat_dpdk.h:133:
+typedef struct {
Patch 4:
--------
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#1727: FILE: drivers/net/ena/ena_platform.h:49:
+#define ena_assert_msg(cond, msg) ^I^I\$
prev parent reply other threads:[~2016-03-10 12:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 20:05 Jan Medala
2016-03-07 20:05 ` [dpdk-dev] [PATCH v5 1/4] ena: Amazon ENA documentation Jan Medala
2016-03-09 12:39 ` Thomas Monjalon
2016-03-10 14:47 ` Hunt, David
2016-03-07 20:05 ` [dpdk-dev] [PATCH v5 2/4] ena: Amazon ENA communication laye Jan Medala
2016-03-09 12:55 ` Thomas Monjalon
2016-03-07 20:05 ` [dpdk-dev] [PATCH v5 3/4] ena: Amazon ENA communication layer for DPDK platform Jan Medala
2016-03-07 20:05 ` [dpdk-dev] [PATCH v5 4/4] ena: DPDK polling-mode driver for Amazon Elastic Network Adapters (ENA) Jan Medala
2016-03-10 15:22 ` Hunt, David
2016-03-09 11:34 ` [dpdk-dev] [PATCH v5 0/4] " Jan Mędala
2016-03-10 12:00 ` Bruce Richardson [this message]
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=20160310120000.GF14712@bricha3-MOBL3 \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=jan@semihalf.com \
--cc=matua@amazon.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).