From: Stephen Rothwell <sfr@canb•auug.org.au>
To: "Matias Bjørling" <m@bjorling•me>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
"Javier González" <javier@cnexlabs•com>
Subject: linux-next: build warning after merge of the lightnvm tree
Date: Wed, 4 May 2016 15:52:03 +1000 [thread overview]
Message-ID: <20160504155203.0a90ee6b@canb.auug.org.au> (raw)
Hi Matias,
After merging the lightnvm tree, today's linux-next build (powerpc
allyesconfig) produced this warning:
In file included from include/linux/swab.h:4:0,
from include/uapi/linux/byteorder/big_endia
n.h:12,
from include/linux/byteorder/big_endian.h:4
,
from arch/powerpc/include/uapi/asm/byteorde
r.h:13,
from include/asm-generic/bitops/le.h:5,
from arch/powerpc/include/asm/bitops.h:279,
from include/linux/bitops.h:36,
from include/linux/kernel.h:10,
from include/linux/list.h:8,
from include/linux/pci.h:25,
from drivers/nvme/host/nvme.h:18,
from drivers/nvme/host/lightnvm.c:23:
drivers/nvme/host/lightnvm.c: In function 'nvme_nvm_rqtocmd'
:
include/uapi/linux/byteorder/big_endian.h:30:52: warning: passing argument 1 of '__fswab64' makes integer from pointer without a cast [-Wint-conversion]
#define __cpu_to_le64(x) ((__force __le64)__swab64((x)))
^
include/uapi/linux/swab.h:126:12: note: in definition of macro '__swab64'
__fswab64(x))
^
include/linux/byteorder/generic.h:85:21: note: in expansion of macro '__cpu_to_le64'
#define cpu_to_le64 __cpu_to_le64
^
drivers/nvme/host/lightnvm.c:472:22: note: in expansion of macro 'cpu_to_le64'
c->ph_rw.metadata = cpu_to_le64(rqd->meta_list);
^
include/uapi/linux/swab.h:68:41: note: expected '__u64 {aka long long unsigned int}' but argument is of type 'void *'
static inline __attribute_const__ __u64 __fswab64(__u64 val)
^
Introduced by commit
a34b1eb78e21 ("lightnvm: enable metadata to be sent to device")
--
Cheers,
Stephen Rothwell
next reply other threads:[~2016-05-04 5:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 5:52 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-09-15 3:42 linux-next: build warning after merge of the lightnvm tree Stephen Rothwell
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=20160504155203.0a90ee6b@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=javier@cnexlabs$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=m@bjorling$(echo .)me \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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