linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Gonglei <arei.gonglei@huawei.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
	qemu-devel@nongnu.org, virtio-dev@lists.oasis-open.org,
	virtualization@lists.linux-foundation.org,
	linux-crypto@vger.kernel.org, luonengjun@huawei.com,
	mst@redhat.com, stefanha@redhat.com, weidong.huang@huawei.com,
	wu.wubin@huawei.com, xin.zeng@intel.com,
	claudio.fontana@huawei.com, herbert@gondor.apana.org.au,
	pasic@linux.vnet.ibm.com, davem@davemloft.net,
	jianjay.zhou@huawei.com, hanweidong@huawei.com,
	arei.gonglei@hotmail.com, cornelia.huck@de.ibm.com,
	xuquan8@huawei.com, longpeng2@huawei.com,
	salvatore.benedetto@intel.com, Gonglei <arei.gonglei@huawei.com>
Subject: Re: [PATCH v3] crypto: add virtio-crypto driver
Date: Tue, 29 Nov 2016 00:02:18 +0800	[thread overview]
Message-ID: <201611282337.Z6RGmXfk%fengguang.wu@intel.com> (raw)
In-Reply-To: <1480334903-6672-2-git-send-email-arei.gonglei@huawei.com>

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

Hi Gonglei,

[auto build test ERROR on cryptodev/master]
[also build test ERROR on v4.9-rc7 next-20161128]
[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/Gonglei/crypto-add-virtio-crypto-driver/20161128-214706
base:   https://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git master
config: sparc-allmodconfig (attached as .config)
compiler: sparc64-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705
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=sparc 

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

   In file included from arch/sparc/include/asm/topology.h:4:0,
                    from include/linux/topology.h:35,
                    from include/linux/gfp.h:8,
                    from include/linux/kmod.h:22,
                    from include/linux/module.h:13,
                    from drivers/crypto/virtio/virtio_crypto_mgr.c:21:
   drivers/crypto/virtio/virtio_crypto_common.h: In function 'virtio_crypto_get_current_node':
>> arch/sparc/include/asm/topology_64.h:44:44: error: implicit declaration of function 'cpu_data' [-Werror=implicit-function-declaration]
    #define topology_physical_package_id(cpu) (cpu_data(cpu).proc_id)
                                               ^
>> drivers/crypto/virtio/virtio_crypto_common.h:118:9: note: in expansion of macro 'topology_physical_package_id'
     return topology_physical_package_id(smp_processor_id());
            ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> arch/sparc/include/asm/topology_64.h:44:57: error: request for member 'proc_id' in something not a structure or union
    #define topology_physical_package_id(cpu) (cpu_data(cpu).proc_id)
                                                            ^
>> drivers/crypto/virtio/virtio_crypto_common.h:118:9: note: in expansion of macro 'topology_physical_package_id'
     return topology_physical_package_id(smp_processor_id());
            ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
   cc1: some warnings being treated as errors

vim +/topology_physical_package_id +118 drivers/crypto/virtio/virtio_crypto_common.h

   102	};
   103	
   104	int virtcrypto_devmgr_add_dev(struct virtio_crypto *vcrypto_dev);
   105	struct list_head *virtcrypto_devmgr_get_head(void);
   106	void virtcrypto_devmgr_rm_dev(struct virtio_crypto *vcrypto_dev);
   107	struct virtio_crypto *virtcrypto_devmgr_get_first(void);
   108	int virtcrypto_dev_in_use(struct virtio_crypto *vcrypto_dev);
   109	int virtcrypto_dev_get(struct virtio_crypto *vcrypto_dev);
   110	void virtcrypto_dev_put(struct virtio_crypto *vcrypto_dev);
   111	int virtcrypto_dev_started(struct virtio_crypto *vcrypto_dev);
   112	struct virtio_crypto *virtcrypto_get_dev_node(int node);
   113	int virtcrypto_dev_start(struct virtio_crypto *vcrypto);
   114	void virtcrypto_dev_stop(struct virtio_crypto *vcrypto);
   115	
   116	static inline int virtio_crypto_get_current_node(void)
   117	{
 > 118		return topology_physical_package_id(smp_processor_id());
   119	}
   120	
   121	int virtio_crypto_algs_register(void);
   122	void virtio_crypto_algs_unregister(void);
   123	
   124	#endif /* _VIRITO_CRYPTO_COMMON_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: 47776 bytes --]

  parent reply	other threads:[~2016-11-28 16:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-28 12:08 [PATCH v3] virtio-crypto: add Linux driver Gonglei
2016-11-28 12:08 ` [PATCH v3] crypto: add virtio-crypto driver Gonglei
2016-11-28 13:12   ` Cornelia Huck
2016-11-29  1:37     ` [virtio-dev] " Gonglei (Arei)
2016-11-29  9:44       ` Cornelia Huck
2016-11-29 11:50         ` Gonglei (Arei)
2016-11-28 16:02   ` kbuild test robot [this message]
2016-11-28 16:20   ` Stefan Hajnoczi
2016-11-28 17:19     ` Michael S. Tsirkin
2016-11-28 17:37       ` Halil Pasic
2016-11-29  3:40         ` Gonglei (Arei)
2016-11-29  3:32       ` Gonglei (Arei)
2016-11-29  6:47       ` Gonglei (Arei)
2016-11-29  8:22       ` Gonglei (Arei)
2016-11-29  9:25         ` Stefan Hajnoczi
2016-11-29  9:29           ` Cornelia Huck
2016-11-29 11:46             ` Gonglei (Arei)
2016-11-29  9:31           ` Gonglei (Arei)

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=201611282337.Z6RGmXfk%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=arei.gonglei@hotmail.com \
    --cc=arei.gonglei@huawei.com \
    --cc=claudio.fontana@huawei.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=davem@davemloft.net \
    --cc=hanweidong@huawei.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=jianjay.zhou@huawei.com \
    --cc=kbuild-all@01.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longpeng2@huawei.com \
    --cc=luonengjun@huawei.com \
    --cc=mst@redhat.com \
    --cc=pasic@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=salvatore.benedetto@intel.com \
    --cc=stefanha@redhat.com \
    --cc=virtio-dev@lists.oasis-open.org \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=weidong.huang@huawei.com \
    --cc=wu.wubin@huawei.com \
    --cc=xin.zeng@intel.com \
    --cc=xuquan8@huawei.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;
as well as URLs for NNTP newsgroup(s).