All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: David Lebrun <david.lebrun@uclouvain.be>
Cc: kbuild-all@01.org, netdev@vger.kernel.org,
	David Lebrun <david.lebrun@uclouvain.be>
Subject: Re: [PATCH net-next] ipv6: sr: add missing Kbuild export for header files
Date: Sat, 14 Jan 2017 12:07:24 +0800	[thread overview]
Message-ID: <201701141219.bDf5ZI5d%fengguang.wu@intel.com> (raw)
In-Reply-To: <1484299564-6165-1-git-send-email-david.lebrun@uclouvain.be>

[-- Attachment #1: Type: text/plain, Size: 782 bytes --]

Hi David,

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

url:    https://github.com/0day-ci/linux/commits/David-Lebrun/ipv6-sr-add-missing-Kbuild-export-for-header-files/20170114-095347
config: x86_64-randconfig-n0-01141038 (attached as .config)
compiler: gcc-4.8 (Debian 4.8.4-1) 4.8.4
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All warnings (new ones prefixed by >>):

>> ./usr/include/linux/seg6.h:21: found __[us]{8,16,32,64} type without #include <linux/types.h>
>> ./usr/include/linux/seg6_hmac.h:11: found __[us]{8,16,32,64} type without #include <linux/types.h>

---
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: 26743 bytes --]

      reply	other threads:[~2017-01-14  4:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-13  9:26 [PATCH net-next] ipv6: sr: add missing Kbuild export for header files David Lebrun
2017-01-14  4:07 ` kbuild test robot [this message]

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=201701141219.bDf5ZI5d%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=david.lebrun@uclouvain.be \
    --cc=kbuild-all@01.org \
    --cc=netdev@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 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.