All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
To: Giuseppe Longo <giuseppelng@gmail.com>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] iptables-nftables: function nft_chain_zero_counters added.
Date: Mon, 17 Jun 2013 15:41:24 +0300	[thread overview]
Message-ID: <51BF03F4.4040300@linux.intel.com> (raw)
In-Reply-To: <CAFpD06SurkbCHH=54yPWwF06doyH5tnRbX4_ODA8Rj9g41QruA@mail.gmail.com>

Hi Giuseppe,

> I runned checkscript.pl with my patch, but i don't get any style issues.
> This is the output:
>
> ./scripts/checkpatch.pl --file /home/giuseppe/nft_chain_zero_counters.patch
> /home/giuseppe/nft_chain_zero_counters.patch:83: ERROR: trailing whitespace
> /home/giuseppe/nft_chain_zero_counters.patch:92: ERROR: trailing whitespace
> total: 2 errors, 0 warnings, 141 lines checked

It's due to --file option you used.

I get that:

WARNING: line over 80 characters
#56: FILE: iptables/nft.c:2884:
+        nlh = nft_chain_nlmsg_build_hdr(buf, NFT_MSG_NEWCHAIN, h->family,

I ran it like: ./checkpatch.pl --no-tree <your patch>

--file option is for a plain source file, not a patch file.

Tomasz

  reply	other threads:[~2013-06-17 12:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-17  9:26 [PATCH v3 1/2] iptables-nftables: function nft_chain_zero_counters added Giuseppe Longo
2013-06-17  9:26 ` [PATCH v3 2/2] xtables: function zero_entries removed Giuseppe Longo
2013-06-17 10:13 ` [PATCH v3 1/2] iptables-nftables: function nft_chain_zero_counters added Tomasz Bursztyka
2013-06-17 11:29   ` Pablo Neira Ayuso
2013-06-17 12:22     ` Giuseppe Longo
2013-06-17 12:41       ` Tomasz Bursztyka [this message]
2013-06-17 13:17   ` Giuseppe Longo
2013-06-18  4:50     ` Tomasz Bursztyka

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=51BF03F4.4040300@linux.intel.com \
    --to=tomasz.bursztyka@linux.intel.com \
    --cc=giuseppelng@gmail.com \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.