From: kbuild test robot <lkp@intel.com>
To: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
Cc: kbuild-all@01.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel@savoirfairelinux.com,
"David S. Miller" <davem@davemloft.net>,
Florian Fainelli <f.fainelli@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@savoirfairelinux.com>
Subject: Re: [PATCH net-next 5/6] net: dsa: mv88e6xxx: add VTU ops
Date: Fri, 17 Feb 2017 18:30:46 +0800 [thread overview]
Message-ID: <201702171845.It2Exz3c%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170217032931.15002-6-vivien.didelot@savoirfairelinux.com>
[-- Attachment #1: Type: text/plain, Size: 3820 bytes --]
Hi Vivien,
[auto build test WARNING on net-next/master]
url: https://github.com/0day-ci/linux/commits/Vivien-Didelot/net-dsa-mv88e6xxx-88E6390-ATU-VTU/20170217-113559
config: openrisc-allmodconfig (attached as .config)
compiler: or32-linux-gcc (GCC) 4.5.1-or32-1.0rc1
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=openrisc
All warnings (new ones prefixed by >>):
drivers/net/dsa/mv88e6xxx/chip.c: In function 'mv88e6xxx_vtu_getnext':
>> drivers/net/dsa/mv88e6xxx/chip.c:1223:6: warning: unused variable 'err'
drivers/net/dsa/mv88e6xxx/chip.c: In function 'mv88e6xxx_vtu_loadpurge':
drivers/net/dsa/mv88e6xxx/chip.c:1234:6: warning: unused variable 'err'
vim +/err +1223 drivers/net/dsa/mv88e6xxx/chip.c
749efcb8 drivers/net/dsa/mv88e6xxx/chip.c Vivien Didelot 2016-09-22 1207 static void mv88e6xxx_port_fast_age(struct dsa_switch *ds, int port)
749efcb8 drivers/net/dsa/mv88e6xxx/chip.c Vivien Didelot 2016-09-22 1208 {
749efcb8 drivers/net/dsa/mv88e6xxx/chip.c Vivien Didelot 2016-09-22 1209 struct mv88e6xxx_chip *chip = ds->priv;
749efcb8 drivers/net/dsa/mv88e6xxx/chip.c Vivien Didelot 2016-09-22 1210 int err;
749efcb8 drivers/net/dsa/mv88e6xxx/chip.c Vivien Didelot 2016-09-22 1211
749efcb8 drivers/net/dsa/mv88e6xxx/chip.c Vivien Didelot 2016-09-22 1212 mutex_lock(&chip->reg_lock);
4663f0f0 drivers/net/dsa/mv88e6xxx/chip.c Vivien Didelot 2017-02-16 1213 err = mv88e6xxx_atu_remove(chip, 0, port);
749efcb8 drivers/net/dsa/mv88e6xxx/chip.c Vivien Didelot 2016-09-22 1214 mutex_unlock(&chip->reg_lock);
749efcb8 drivers/net/dsa/mv88e6xxx/chip.c Vivien Didelot 2016-09-22 1215
749efcb8 drivers/net/dsa/mv88e6xxx/chip.c Vivien Didelot 2016-09-22 1216 if (err)
749efcb8 drivers/net/dsa/mv88e6xxx/chip.c Vivien Didelot 2016-09-22 1217 netdev_err(ds->ports[port].netdev, "failed to flush ATU\n");
749efcb8 drivers/net/dsa/mv88e6xxx/chip.c Vivien Didelot 2016-09-22 1218 }
749efcb8 drivers/net/dsa/mv88e6xxx/chip.c Vivien Didelot 2016-09-22 1219
5bdaf1f8 drivers/net/dsa/mv88e6xxx/chip.c Vivien Didelot 2017-02-16 1220 static int mv88e6xxx_vtu_getnext(struct mv88e6xxx_chip *chip,
b4e47c0f drivers/net/dsa/mv88e6xxx/chip.c Vivien Didelot 2016-09-29 1221 struct mv88e6xxx_vtu_entry *entry)
15d7d7d4 drivers/net/dsa/mv88e6xxx.c Vivien Didelot 2016-05-10 1222 {
5bdaf1f8 drivers/net/dsa/mv88e6xxx/chip.c Vivien Didelot 2017-02-16 @1223 int err;
7dad08d7 drivers/net/dsa/mv88e6xxx.c Vivien Didelot 2015-08-13 1224
5bdaf1f8 drivers/net/dsa/mv88e6xxx/chip.c Vivien Didelot 2017-02-16 1225 if (!mv88e6xxx_has_vtu(chip))
5bdaf1f8 drivers/net/dsa/mv88e6xxx/chip.c Vivien Didelot 2017-02-16 1226 return -EOPNOTSUPP;
7dad08d7 drivers/net/dsa/mv88e6xxx.c Vivien Didelot 2015-08-13 1227
ab37f7c5 drivers/net/dsa/mv88e6xxx/chip.c Vivien Didelot 2017-02-16 1228 return chip->info->ops->vtu_getnext(chip, entry);
7dad08d7 drivers/net/dsa/mv88e6xxx.c Vivien Didelot 2015-08-13 1229 }
7dad08d7 drivers/net/dsa/mv88e6xxx.c Vivien Didelot 2015-08-13 1230
5bdaf1f8 drivers/net/dsa/mv88e6xxx/chip.c Vivien Didelot 2017-02-16 1231 static int mv88e6xxx_vtu_loadpurge(struct mv88e6xxx_chip *chip,
:::::: The code at line 1223 was first introduced by commit
:::::: 5bdaf1f8afa18557bba4f236a53dee259a0469c4 net: dsa: mv88e6xxx: move VTU code to its own file
:::::: TO: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
:::::: CC: 0day robot <fengguang.wu@intel.com>
---
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: 39973 bytes --]
next prev parent reply other threads:[~2017-02-17 10:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 3:29 [PATCH net-next 0/6] net: dsa: mv88e6xxx: 88E6390 ATU/VTU Vivien Didelot
2017-02-17 3:29 ` [PATCH net-next 1/6] net: dsa: mv88e6xxx: add port mask helper Vivien Didelot
2017-02-17 3:29 ` [PATCH net-next 2/6] net: dsa: mv88e6xxx: move ATU code in its own file Vivien Didelot
2017-02-17 3:29 ` [PATCH net-next 3/6] net: dsa: mv88e6xxx: add support for 6390 ATU Move Vivien Didelot
2017-02-17 3:29 ` [PATCH net-next 4/6] net: dsa: mv88e6xxx: move VTU code to its own file Vivien Didelot
2017-02-17 3:29 ` [PATCH net-next 5/6] net: dsa: mv88e6xxx: add VTU ops Vivien Didelot
2017-02-17 10:30 ` kbuild test robot [this message]
2017-02-17 3:29 ` [PATCH net-next 6/6] net: dsa: mv88e6xxx: add support for 6390 VTU Vivien Didelot
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=201702171845.It2Exz3c%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kbuild-all@01.org \
--cc=kernel@savoirfairelinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@savoirfairelinux.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
all inboxes | Powered by JetHome®