netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Florian Westphal <fw@strlen.de>
Cc: kbuild-all@01.org, netfilter-devel@vger.kernel.org,
	Florian Westphal <fw@strlen.de>
Subject: Re: [PATCH nf-next] netfilter: meta: secpath support
Date: Wed, 13 Dec 2017 15:16:22 +0800	[thread overview]
Message-ID: <201712131306.izdruXUk%fengguang.wu@intel.com> (raw)
In-Reply-To: <20171201124021.20973-2-fw@strlen.de>

Hi Florian,

I love your patch! Perhaps something to improve:

[auto build test WARNING on nf-next/master]

url:    https://github.com/0day-ci/linux/commits/Florian-Westphal/netfilter-meta-secpath-support/20171204-124857
base:   https://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf-next.git master
reproduce:
        # apt-get install sparse
        make ARCH=x86_64 allmodconfig
        make C=1 CF=-D__CHECK_ENDIAN__


sparse warnings: (new ones prefixed by >>)


Please review and possibly fold the followup patch.

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

  parent reply	other threads:[~2017-12-13 15:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-01 12:40 [PATCH next] nftables: add inbound ipsec matching Florian Westphal
2017-12-01 12:40 ` [PATCH nf-next] netfilter: meta: secpath support Florian Westphal
2017-12-01 12:40   ` Florian Westphal
2017-12-01 12:53   ` Arturo Borrero Gonzalez
2017-12-01 13:07     ` Florian Westphal
2017-12-13  7:16   ` kbuild test robot [this message]
2017-12-13  7:16   ` [RFC PATCH] netfilter: meta: nft_meta_get_validate() can be static kbuild test robot
2017-12-13 16:42     ` Pablo Neira Ayuso
2017-12-01 12:40 ` [PATCH libnftnl] meta: secpath support Florian Westphal
2017-12-01 12:40 ` [PATCH nft] meta: add " Florian Westphal

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=201712131306.izdruXUk%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=fw@strlen.de \
    --cc=kbuild-all@01.org \
    --cc=netfilter-devel@vger.kernel.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).