automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: John McNamara <john.mcnamara@intel.com>
Subject: [dpdk-test-report] |WARNING| pw84657 [PATCH v1] license: add licenses for exception cases
Date: Tue,  1 Dec 2020 15:27:42 +0100 (CET)	[thread overview]
Message-ID: <20201201142742.3B1EDC9AE@dpdk.org> (raw)
In-Reply-To: <20201201142646.2522769-1-john.mcnamara@intel.com>

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

_coding style issues_


ERROR:TRAILING_WHITESPACE: trailing whitespace
#92: FILE: license/bsd-2-clause.txt:6:
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. $

total: 1 errors, 0 warnings, 14 lines checked

       reply	other threads:[~2020-12-01 14:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20201201142646.2522769-1-john.mcnamara@intel.com>
2020-12-01 14:27 ` checkpatch [this message]
2020-12-01 16:34 ` [dpdk-test-report] |SUCCESS| pw84657 " 0-day Robot

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=20201201142742.3B1EDC9AE@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=john.mcnamara@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).