From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC net-next Patch 3/3] net: bridge: mrp: Add netlink support to configure MRP
Date: Fri, 10 Jan 2020 22:27:05 +0800 [thread overview]
Message-ID: <202001102254.WqLyeZce%lkp@intel.com> (raw)
In-Reply-To: <20200109150640.532-4-horatiu.vultur@microchip.com>
[-- Attachment #1: Type: text/plain, Size: 1465 bytes --]
Hi Horatiu,
[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on net-next/master]
[also build test WARNING on next-20200109]
[cannot apply to linux/master net/master linus/master v5.5-rc5]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Horatiu-Vultur/net-bridge-mrp-Add-support-for-Media-Redundancy-Protocol-MRP/20200110-153712
base: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git 9f120e7659b022c790416a3409dfdb54b4a775d5
config: i386-tinyconfig (attached as .config)
compiler: gcc-7 (Debian 7.5.0-3) 7.5.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> warning: include/uapi/linux/if_bridge.h: leak CONFIG_BRIDGE_MRP to user-space
6 real 10 user 4 sys 246.58% cpu make INSTALL_HDR_PATH=/tmp/usr/src/linux-headers-i386-tinyconfig-72de9bd63f9e89aa0294410c6ea6147f97b475bd headers_install
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org Intel Corporation
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 7205 bytes --]
next prev parent reply other threads:[~2020-01-10 14:27 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 15:06 [RFC net-next Patch 0/3] net: bridge: mrp: Add support for Media Redundancy Protocol(MRP) Horatiu Vultur
2020-01-09 15:06 ` [Bridge] " Horatiu Vultur
2020-01-09 15:06 ` [RFC net-next Patch 1/3] net: bridge: mrp: Add support for Media Redundancy Protocol Horatiu Vultur
2020-01-09 15:06 ` [Bridge] " Horatiu Vultur
2020-01-09 15:06 ` [RFC net-next Patch 2/3] net: bridge: mrp: Integrate MRP into the bridge Horatiu Vultur
2020-01-09 15:06 ` [Bridge] " Horatiu Vultur
2020-01-09 15:06 ` [RFC net-next Patch 3/3] net: bridge: mrp: Add netlink support to configure MRP Horatiu Vultur
2020-01-09 15:06 ` [Bridge] " Horatiu Vultur
2020-01-10 14:27 ` kbuild test robot [this message]
2020-01-10 14:52 ` kbuild test robot
2020-01-09 16:19 ` [RFC net-next Patch 0/3] net: bridge: mrp: Add support for Media Redundancy Protocol(MRP) Stephen Hemminger
2020-01-09 16:19 ` [Bridge] " Stephen Hemminger
2020-01-09 17:41 ` Asbjørn Sloth Tønnesen
2020-01-09 17:41 ` Asbjørn Sloth Tønnesen
2020-01-10 9:02 ` Horatiu Vultur
2020-01-10 9:02 ` [Bridge] " Horatiu Vultur
2020-01-10 15:36 ` Stephen Hemminger
2020-01-10 15:36 ` [Bridge] " Stephen Hemminger
2020-01-10 14:13 ` Nikolay Aleksandrov
2020-01-10 14:13 ` [Bridge] " Nikolay Aleksandrov
2020-01-10 15:38 ` Nikolay Aleksandrov
2020-01-10 15:38 ` [Bridge] " Nikolay Aleksandrov
2020-01-10 16:04 ` Horatiu Vultur
2020-01-10 16:04 ` [Bridge] " Horatiu Vultur
2020-01-10 16:21 ` Vladimir Oltean
2020-01-10 16:21 ` [Bridge] " Vladimir Oltean
2020-01-10 16:48 ` Andrew Lunn
2020-01-10 16:48 ` [Bridge] " Andrew Lunn
2020-01-10 17:25 ` Horatiu Vultur
2020-01-10 17:25 ` [Bridge] " Horatiu Vultur
2020-01-10 17:56 ` Andrew Lunn
2020-01-10 17:56 ` [Bridge] " Andrew Lunn
2020-01-10 20:12 ` Horatiu Vultur
2020-01-10 20:12 ` [Bridge] " Horatiu Vultur
2020-01-10 20:33 ` Andrew Lunn
2020-01-10 20:33 ` [Bridge] " Andrew Lunn
2020-01-10 19:27 ` David Miller
2020-01-10 19:27 ` [Bridge] " David Miller
2020-01-10 20:03 ` nikolay
2020-01-10 20:03 ` [Bridge] " nikolay
2020-01-10 20:24 ` Horatiu Vultur
2020-01-10 20:24 ` [Bridge] " Horatiu Vultur
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=202001102254.WqLyeZce%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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.