From: kbuild test robot <lkp@intel.com>
To: Joerg Roedel <jroedel@suse.de>
Cc: kbuild-all@01.org, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Christoph Hellwig <hch@lst.de>
Subject: [vhost:linux-next 3/23] include/linux/swiotlb.h:105:20: error: static declaration of 'is_swiotlb_active' follows non-static declaration
Date: Wed, 6 Feb 2019 03:37:37 +0800 [thread overview]
Message-ID: <201902060335.RnfdRtuU%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3120 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git linux-next
head: 104f89a60ef5ec77d6f559eac4676844b3480740
commit: 155fcd8511de5f99c27a726e9153b87cce528b6e [3/23] swiotlb: Add is_swiotlb_active() function
config: i386-tinyconfig (attached as .config)
compiler: gcc-8 (Debian 8.2.0-14) 8.2.0
reproduce:
git checkout 155fcd8511de5f99c27a726e9153b87cce528b6e
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
In file included from arch/x86/include/asm/swiotlb.h:5,
from arch/x86/include/asm/dma-mapping.h:13,
from include/linux/dma-mapping.h:261,
from include/linux/skbuff.h:34,
from include/net/net_namespace.h:36,
from include/linux/inet.h:46,
from include/linux/sunrpc/msg_prot.h:204,
from include/linux/sunrpc/auth.h:16,
from include/linux/nfs_fs.h:31,
from init/do_mounts.c:22:
include/linux/swiotlb.h:100:22: error: static declaration of 'swiotlb_max_mapping_size' follows non-static declaration
static inline size_t swiotlb_max_mapping_size(struct device *dev)
^~~~~~~~~~~~~~~~~~~~~~~~
include/linux/swiotlb.h:65:8: note: previous declaration of 'swiotlb_max_mapping_size' was here
size_t swiotlb_max_mapping_size(struct device *dev);
^~~~~~~~~~~~~~~~~~~~~~~~
>> include/linux/swiotlb.h:105:20: error: static declaration of 'is_swiotlb_active' follows non-static declaration
static inline bool is_swiotlb_active(void)
^~~~~~~~~~~~~~~~~
include/linux/swiotlb.h:66:6: note: previous declaration of 'is_swiotlb_active' was here
bool is_swiotlb_active(void);
^~~~~~~~~~~~~~~~~
vim +/is_swiotlb_active +105 include/linux/swiotlb.h
76
77 bool swiotlb_map(struct device *dev, phys_addr_t *phys, dma_addr_t *dma_addr,
78 size_t size, enum dma_data_direction dir, unsigned long attrs);
79 void __init swiotlb_exit(void);
80 unsigned int swiotlb_max_segment(void);
81 #else
82 #define swiotlb_force SWIOTLB_NO_FORCE
83 static inline bool is_swiotlb_buffer(phys_addr_t paddr)
84 {
85 return false;
86 }
87 static inline bool swiotlb_map(struct device *dev, phys_addr_t *phys,
88 dma_addr_t *dma_addr, size_t size, enum dma_data_direction dir,
89 unsigned long attrs)
90 {
91 return false;
92 }
93 static inline void swiotlb_exit(void)
94 {
95 }
96 static inline unsigned int swiotlb_max_segment(void)
97 {
98 return 0;
99 }
> 100 static inline size_t swiotlb_max_mapping_size(struct device *dev)
101 {
102 return SIZE_MAX;
103 }
104
> 105 static inline bool is_swiotlb_active(void)
106 {
107 return false;
108 }
109 #endif /* CONFIG_SWIOTLB */
110
---
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: 6514 bytes --]
reply other threads:[~2019-02-05 19:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201902060335.RnfdRtuU%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=hch@lst.de \
--cc=jroedel@suse.de \
--cc=kbuild-all@01.org \
--cc=konrad.wilk@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox