From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Harry van Haaren <harry.van.haaren@intel.com>
Subject: [dpdk-test-report] |WARNING| pw19444 [PATCH 11/15] event/sw: add scheduling logic
Date: Mon, 16 Jan 2017 16:41:52 +0100 (CET) [thread overview]
Message-ID: <20170116154152.5EEB0F95F@dpdk.org> (raw)
In-Reply-To: <1484581255-148720-12-git-send-email-harry.van.haaren@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/19444
_coding style issues_
WARNING:LONG_LINE: line over 90 characters
#440: FILE: drivers/event/sw/sw_evdev_scheduler.c:322:
+ const struct iq_ring *dest_iq_ptr = dest_qid_ptr->iq[dest_iq];
WARNING:LONG_LINE: line over 90 characters
#566: FILE: drivers/event/sw/sw_evdev_scheduler.c:448:
+ rob_entry->fragments[rob_entry->num_fragments++] = *qe;
WARNING:LONG_LINE: line over 90 characters
#669: FILE: drivers/event/sw/sw_evdev_scheduler.c:551:
+ in_pkts += sw_schedule_pull_port_no_reorder(sw, i);
total: 0 errors, 3 warnings, 623 lines checked
parent reply other threads:[~2017-01-16 15:41 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1484581255-148720-12-git-send-email-harry.van.haaren@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=20170116154152.5EEB0F95F@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=harry.van.haaren@intel.com \
--cc=test-report@dpdk.org \
/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).