automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Wei Dai <wei.dai@intel.com>
Subject: [dpdk-test-report] |WARNING| pw39553 [PATCH v8] ethdev: check Rx/Tx offloads
Date: Wed,  9 May 2018 12:28:14 +0200 (CEST)	[thread overview]
Message-ID: <20180509102814.9A3861B168@dpdk.org> (raw)
In-Reply-To: <49759EB36A64CF4892C1AFEC9231E8D66CF7EF32@PGSMSX111.gar.corp.intel.com>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/39553

_coding style issues_


WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#68: 
To: Dai, Wei <wei.dai@intel.com>; Yigit, Ferruh <ferruh.yigit@intel.com>; thomas@monjalon.net; Doherty, Declan <declan.doherty@intel.com>; linville@tuxdriver.com; mw@semihalf.com; mk@semihalf.com; gtzalik@amazon.com; evgenys@amazon.com; ravi1.kumar@amd.com; shepard.siegel@atomicrules.com; ed.czeck@atomicrules.com; john.miller@atomicrules.com; ajit.khaparde@broadcom.com; somnath.kotur@broadcom.com; jerin.jacob@caviumnetworks.com; maciej.czekaj@caviumnetworks.com; shijith.thotton@cavium.com; ssrinivasan@cavium.com; santosh.shukla@caviumnetworks.com; rahul.lakkireddy@chelsio.com; ohndale@cisco.com; hyonkim@cisco.com; Lu, Wenzhuo <wenzhuo.lu@intel.com>; Ananyev, Konstantin <konstantin.ananyev@intel.com>; Xing, Beilei <beilei.xing@intel.com>; Zhang, Qi Z <qi.z.zhang@intel.com>; Wang, Xiao W <xiao.w.wang@intel.com>; Wu, Jingjing <jingjing.wu@intel.com>; tdu@semihalf.com; dima@marvell.com; nsamsono@marvell.com; jianbo.liu@arm.com; adrien.mazarguil@6wind.com; nelio.laranjeiro@6wind.com; yskoh@mellanox.com; matan@mellanox.com; vido@cesnet.cz; alejandro.lucero@netronome.com; emant.agrawal@nxp.com; shreyansh.jain@nxp.com; hemant.agrawal@nxp.com; harish.patil@cavium.com; rasesh.mody@cavium.com; asesh.mody@cavium.com; shahed.shaikh@cavium.com; yongwang@vmware.com; maxime.coquelin@redhat.com; mtetsuyah@gmail.com; Bie, Tiwei <tiwei.bie@intel.com>; Legacy, Allain (Wind River) <allain.legacy@windriver.com>; Peters, Matt (Wind River) <matt.peters@windriver.com>; pascal.mazon@6wind.com; Richardson, Bruce <bruce.richardson@intel.com>; gaetan.rivet@6wind.com; Singh, Jasvinder <jasvinder.singh@intel.com>; Dumitrescu, Cristian <cristian.dumitrescu@intel.com>

ERROR:DOS_LINE_ENDINGS: DOS line endings
#130: FILE: :474:
+^Iuint64_t offloads;^M$

ERROR:DOS_LINE_ENDINGS: DOS line endings
#138: FILE: :481:
+^Ioffloads = tx_conf->offloads | dev->data->dev_conf.txmode.offloads;^M$

ERROR:CORRUPTED_PATCH: patch seems to be corrupt (line wrapped?)
#139: FILE: :481:


ERROR:DOS_LINE_ENDINGS: DOS line endings
#143: FILE: :482:
+^Irc = sfc_tx_qinit(sa, tx_queue_id, nb_tx_desc, socket_id,^M$

ERROR:DOS_LINE_ENDINGS: DOS line endings
#144: FILE: :483:
+^I^I^I  tx_conf, offloads);^M$

ERROR:DOS_LINE_ENDINGS: DOS line endings
#168: FILE: drivers/net/sfc/sfc_ethdev.c:416:
+^Iuint64_t offloads;^M$

ERROR:DOS_LINE_ENDINGS: DOS line endings
#175: FILE: drivers/net/sfc/sfc_ethdev.c:423:
+^Ioffloads = rx_conf->offloads | dev->data->dev_conf.rxmode.offloads;^M$

total: 7 errors, 1 warnings, 0 checks, 46 lines checked

           reply	other threads:[~2018-05-09 10:28 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <49759EB36A64CF4892C1AFEC9231E8D66CF7EF32@PGSMSX111.gar.corp.intel.com>]

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=20180509102814.9A3861B168@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=test-report@dpdk.org \
    --cc=wei.dai@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).