mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Pavel Machek <pavel@denx.de>
Cc: kbuild-all@01.org, Woojung.Huh@microchip.com,
	nathan.leigh.conrad@gmail.com,
	vivien.didelot@savoirfairelinux.com, f.fainelli@gmail.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Tristram.Ha@micrel.com, andrew@lunn.ch, pavel@denx.de
Subject: Re: [PATCH] DSA support for Micrel KSZ8895
Date: Tue, 29 Aug 2017 23:33:30 +0800	[thread overview]
Message-ID: <201708292347.bZWZXRAV%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170827123658.GA727@amd>

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

Hi Pavel,

[auto build test ERROR on net-next/master]
[also build test ERROR on v4.13-rc7 next-20170829]
[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/Pavel-Machek/DSA-support-for-Micrel-KSZ8895/20170829-220156
config: xtensa-allmodconfig (attached as .config)
compiler: xtensa-linux-gcc (GCC) 4.9.0
reproduce:
        wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        make.cross ARCH=xtensa 

All error/warnings (new ones prefixed by >>):

   In file included from drivers/net/dsa/microchip/ksz_common.c:31:0:
>> drivers/net/dsa/microchip/ksz_9477_reg.h:19:2: error: #error This is not switch we have
    #error This is not switch we have
     ^
--
   drivers/net/dsa/microchip/ksz_8895.c: In function 'ksz_reset_switch':
   drivers/net/dsa/microchip/ksz_8895.c:109:21: warning: unused variable 'dev' [-Wunused-variable]
     struct ksz_device *dev = ds->priv;
                        ^
   drivers/net/dsa/microchip/ksz_8895.c: In function 'ksz_br_join':
   drivers/net/dsa/microchip/ksz_8895.c:262:21: warning: unused variable 'dev' [-Wunused-variable]
     struct ksz_device *dev = ds->priv;
                        ^
   drivers/net/dsa/microchip/ksz_8895.c: In function 'ksz_br_leave':
   drivers/net/dsa/microchip/ksz_8895.c:270:21: warning: unused variable 'dev' [-Wunused-variable]
     struct ksz_device *dev = ds->priv;
                        ^
   drivers/net/dsa/microchip/ksz_8895.c: At top level:
>> drivers/net/dsa/microchip/ksz_8895.c:469:12: warning: 'struct switchdev_obj_port_fdb' declared inside parameter list
        struct switchdev_trans *trans)
               ^
>> drivers/net/dsa/microchip/ksz_8895.c:469:12: warning: its scope is only this definition or declaration, which is probably not what you want
   drivers/net/dsa/microchip/ksz_8895.c:497:16: warning: 'struct switchdev_obj_port_fdb' declared inside parameter list
            struct switchdev_trans *trans)
                   ^
   drivers/net/dsa/microchip/ksz_8895.c:503:21: warning: 'struct switchdev_obj_port_fdb' declared inside parameter list
           const struct switchdev_obj_port_fdb *fdb)
                        ^
   drivers/net/dsa/microchip/ksz_8895.c:510:9: warning: 'struct switchdev_obj_port_fdb' declared inside parameter list
            switchdev_obj_dump_cb_t *cb)
            ^
>> drivers/net/dsa/microchip/ksz_8895.c:576:2: error: unknown field 'port_vlan_dump' specified in initializer
     .port_vlan_dump  = ksz_port_vlan_dump,
     ^
>> drivers/net/dsa/microchip/ksz_8895.c:576:2: warning: initialization from incompatible pointer type
   drivers/net/dsa/microchip/ksz_8895.c:576:2: warning: (near initialization for 'ksz_switch_ops.port_fdb_add')
>> drivers/net/dsa/microchip/ksz_8895.c:577:2: error: unknown field 'port_fdb_prepare' specified in initializer
     .port_fdb_prepare = ksz_port_fdb_prepare,
     ^
   drivers/net/dsa/microchip/ksz_8895.c:577:2: warning: initialization from incompatible pointer type
   drivers/net/dsa/microchip/ksz_8895.c:577:2: warning: (near initialization for 'ksz_switch_ops.port_fdb_del')
   drivers/net/dsa/microchip/ksz_8895.c:578:2: warning: initialization from incompatible pointer type
     .port_fdb_dump  = ksz_port_fdb_dump,
     ^
   drivers/net/dsa/microchip/ksz_8895.c:578:2: warning: (near initialization for 'ksz_switch_ops.port_fdb_dump')
   drivers/net/dsa/microchip/ksz_8895.c:579:2: warning: initialization from incompatible pointer type
     .port_fdb_add  = ksz_port_fdb_add,
     ^
   drivers/net/dsa/microchip/ksz_8895.c:579:2: warning: (near initialization for 'ksz_switch_ops.port_fdb_add')
   drivers/net/dsa/microchip/ksz_8895.c:580:2: warning: initialization from incompatible pointer type
     .port_fdb_del  = ksz_port_fdb_del,
     ^
   drivers/net/dsa/microchip/ksz_8895.c:580:2: warning: (near initialization for 'ksz_switch_ops.port_fdb_del')
>> drivers/net/dsa/microchip/ksz_8895.c:584:2: error: unknown field 'port_mdb_dump' specified in initializer
     .port_mdb_dump          = ksz_port_mdb_dump,
     ^
   drivers/net/dsa/microchip/ksz_8895.c:584:2: warning: initialization from incompatible pointer type
   drivers/net/dsa/microchip/ksz_8895.c:584:2: warning: (near initialization for 'ksz_switch_ops.get_rxnfc')

vim +19 drivers/net/dsa/microchip/ksz_9477_reg.h

  > 19	#error This is not switch we have
    20	#ifndef __KSZ9477_REGS_H
    21	#define __KSZ9477_REGS_H
    22	

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

  parent reply	other threads:[~2017-08-29 15:34 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-16  7:55 Pavel Machek
2017-08-16 14:04 ` Andrew Lunn
2017-08-16 14:25   ` Woojung.Huh
2017-08-23  9:09     ` Pavel Machek
2017-08-23 12:42       ` Andrew Lunn
2017-08-23 21:48       ` Woojung.Huh
2017-08-28 10:14         ` Pavel Machek
2017-08-28 13:19           ` Andrew Lunn
2017-08-27 12:36     ` [PATCH] " Pavel Machek
2017-08-27 13:59       ` Andrew Lunn
2017-08-27 16:31       ` Andrew Lunn
2017-08-28  7:02         ` Pavel Machek
2017-08-28 14:09           ` Andrew Lunn
2017-08-28 14:47             ` Maxim Uvarov
2017-08-29  7:41               ` Pavel Machek
2017-08-29 12:26                 ` Andrew Lunn
2017-08-29 21:15                   ` Pavel Machek
2017-08-29 21:23                     ` Florian Fainelli
2017-08-30 10:06                       ` Maxim Uvarov
2017-08-29  7:45             ` Pavel Machek
2017-08-30 21:32               ` Tristram.Ha
2017-08-30 22:00                 ` Andrew Lunn
2017-09-01 12:15                 ` Pavel Machek
2017-09-01 22:18                   ` Florian Fainelli
2017-09-02 15:40                     ` Pavel Machek
2017-09-06  9:14                 ` Maxim Uvarov
2017-09-06 16:47                   ` Tristram.Ha
2017-09-06 17:09                     ` Andrew Lunn
2017-08-27 16:44       ` Andrew Lunn
2017-08-28  6:40         ` Pavel Machek
2017-08-27 16:56       ` Florian Fainelli
2017-08-28  6:47         ` Pavel Machek
2017-08-27 22:03       ` Woojung.Huh
2017-08-29 15:33       ` kbuild test robot [this message]
2017-08-16 18:32   ` Pavel Machek

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=201708292347.bZWZXRAV%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=Tristram.Ha@micrel.com \
    --cc=Woojung.Huh@microchip.com \
    --cc=andrew@lunn.ch \
    --cc=f.fainelli@gmail.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nathan.leigh.conrad@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pavel@denx.de \
    --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®