From: kbuild test robot <lkp@intel•com>
To: Yi-Hung Wei <yihung.wei@gmail•com>
Cc: kbuild-all@01•org, netdev@vger•kernel.org,
Yi-Hung Wei <yihung.wei@gmail•com>,
Pablo Neira Ayuso <pablo@netfilter•org>
Subject: Re: [PATCH 1/2] netfilter: Export nf_ct_{set,destroy}_timeout()
Date: Sat, 23 Mar 2019 22:59:48 +0800 [thread overview]
Message-ID: <201903232252.HCqAk0sT%lkp@intel.com> (raw)
In-Reply-To: <1553276009-39311-1-git-send-email-yihung.wei@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 905 bytes --]
Hi Yi-Hung,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on nf-next/master]
[also build test ERROR on v5.1-rc1 next-20190322]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Yi-Hung-Wei/netfilter-Export-nf_ct_-set-destroy-_timeout/20190323-195349
base: https://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf-next.git master
config: x86_64-rhel (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
>> ERROR: "nf_ct_destroy_timeout" [net/netfilter/xt_CT.ko] undefined!
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 41435 bytes --]
next prev parent reply other threads:[~2019-03-23 15:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-22 17:33 [PATCH 1/2] netfilter: Export nf_ct_{set,destroy}_timeout() Yi-Hung Wei
2019-03-22 17:33 ` [PATCH 2/2] openvswitch: Add timeout support to ct action Yi-Hung Wei
2019-03-23 13:58 ` kbuild test robot
2019-03-23 14:59 ` kbuild test robot [this message]
2019-03-23 16:24 ` [PATCH 1/2] netfilter: Export nf_ct_{set,destroy}_timeout() kbuild test 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=201903232252.HCqAk0sT%lkp@intel.com \
--to=lkp@intel$(echo .)com \
--cc=kbuild-all@01$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pablo@netfilter$(echo .)org \
--cc=yihung.wei@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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