netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [nftables kernel - PATCH 1/2] netfilter: nf_tables: Update uapi nftables netlink header documentation
Date: Fri, 11 Oct 2013 10:43:07 +0200	[thread overview]
Message-ID: <20131011084307.GA3956@localhost> (raw)
In-Reply-To: <1381139880-20311-2-git-send-email-tomasz.bursztyka@linux.intel.com>

On Mon, Oct 07, 2013 at 12:57:59PM +0300, Tomasz Bursztyka wrote:
> Thus all types, attributes, flags and so on get properly updated as the
> very first ones were.

Applying: netfilter: nf_tables: Update uapi nftables netlink header
documentation
/home/pablo/devel/scm/git-kernel/korg/nftables-backup/.git/rebase-apply/patch:76:
trailing whitespace.
 * @NFT_RULE_COMPAT_F_INV: invert the check result
/home/pablo/devel/scm/git-kernel/korg/nftables-backup/.git/rebase-apply/patch:87:
trailing whitespace.
 * @NFTA_RULE_COMPAT_FLAGS: bitmask of enum nft_rule_compat_flags
 * (NLA_U32)
/home/pablo/devel/scm/git-kernel/korg/nftables-backup/.git/rebase-apply/patch:114:
trailing whitespace.
 * @NFTA_BYTEORDER_SIZE: _TODO_ (NLA_U32)
warning: 3 lines add whitespace errors.

Please, mind with whitespace errors at the end of lines. I have fixed
them here.

Applied, thanks.

  reply	other threads:[~2013-10-11  8:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-07  9:57 [nftables kernel - PATCH 0/2] Minor API fixes (mostly documentation) Tomasz Bursztyka
2013-10-07  9:57 ` [nftables kernel - PATCH 1/2] netfilter: nf_tables: Update uapi nftables netlink header documentation Tomasz Bursztyka
2013-10-11  8:43   ` Pablo Neira Ayuso [this message]
2013-10-11  9:10     ` Tomasz Bursztyka
2013-10-07  9:58 ` [nftables kernel - PATCH 2/2] netfilter: nf_tables: Fix the netlink attributes policy for chain Tomasz Bursztyka
2013-10-11  8:43   ` Pablo Neira Ayuso

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=20131011084307.GA3956@localhost \
    --to=pablo@netfilter.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=tomasz.bursztyka@linux.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).