From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Miller <davem@davemloft.net>, Networking <netdev@vger.kernel.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Tomer Tayar <Tomer.Tayar@cavium.com>,
Ram Amrani <Ram.Amrani@cavium.com>,
Manish Rangankar <Manish.Rangankar@cavium.com>,
Chad Dupuis <Chad.Dupuis@cavium.com>,
Yuval Mintz <Yuval.Mintz@cavium.com>
Subject: linux-next: build warnings after merge of the net-next tree
Date: Mon, 20 Mar 2017 17:07:13 +1100 [thread overview]
Message-ID: <20170320170713.71010326@canb.auug.org.au> (raw)
Hi all,
After merging the net-next tree, today's linux-next build (powerpc
allyesconfig) produced thie warnings:
In file included from include/linux/byteorder/big_endian.h:4:0,
from arch/powerpc/include/uapi/asm/byteorder.h:13,
from include/linux/qed/common_hsi.h:36,
from drivers/scsi/qedf/drv_scsi_fw_funcs.h:10,
from drivers/scsi/qedf/drv_fcoe_fw_funcs.h:10,
from drivers/scsi/qedf/drv_fcoe_fw_funcs.c:8:
drivers/scsi/qedf/drv_fcoe_fw_funcs.c: In function 'init_initiator_rw_fcoe_task':
include/uapi/linux/byteorder/big_endian.h:32:26: warning: large integer implicitly truncated to unsigned type [-Woverflow]
#define __cpu_to_le32(x) ((__force __le32)__swab32((x)))
^
include/linux/byteorder/generic.h:87:21: note: in expansion of macro '__cpu_to_le32'
#define cpu_to_le32 __cpu_to_le32
^
drivers/scsi/qedf/drv_fcoe_fw_funcs.c:62:31: note: in expansion of macro 'cpu_to_le32'
t_st_ctx->read_write.rx_id = cpu_to_le32(FCOE_RX_ID);
^
drivers/scsi/qedf/drv_fcoe_fw_funcs.c: In function 'init_initiator_midpath_unsolicited_fcoe_task':
include/uapi/linux/byteorder/big_endian.h:32:26: warning: large integer implicitly truncated to unsigned type [-Woverflow]
#define __cpu_to_le32(x) ((__force __le32)__swab32((x)))
^
include/linux/byteorder/generic.h:87:21: note: in expansion of macro '__cpu_to_le32'
#define cpu_to_le32 __cpu_to_le32
^
drivers/scsi/qedf/drv_fcoe_fw_funcs.c:154:31: note: in expansion of macro 'cpu_to_le32'
t_st_ctx->read_write.rx_id = cpu_to_le32(FCOE_RX_ID);
^
Introduced by commit
be086e7c53f1 ("qed*: Utilize Firmware 8.15.3.0")
--
Cheers,
Stephen Rothwell
next reply other threads:[~2017-03-20 6:07 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 6:07 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-04 4:47 linux-next: build warnings after merge of the net-next tree Stephen Rothwell
2023-09-18 3:15 Stephen Rothwell
2023-09-18 7:43 ` Bagas Sanjaya
2023-06-26 6:29 Stephen Rothwell
2023-09-05 22:55 ` Stephen Rothwell
2023-09-05 23:44 ` Jakub Kicinski
2023-06-13 6:31 Stephen Rothwell
2023-06-20 16:15 ` Jakub Kicinski
2023-06-20 23:12 ` Saeed Mahameed
2022-11-14 7:31 Stephen Rothwell
2022-11-14 8:00 ` Akira Yokosawa
2021-06-15 11:23 Stephen Rothwell
2021-06-15 11:12 Stephen Rothwell
2021-03-18 6:22 Stephen Rothwell
2021-02-18 20:52 Stephen Rothwell
2021-02-19 8:44 ` Stephen Rothwell
2021-02-19 14:57 ` Kalle Valo
2020-12-14 9:10 Stephen Rothwell
2020-12-21 1:28 ` Stephen Rothwell
2021-01-05 6:19 ` Stephen Rothwell
2019-11-05 1:45 Stephen Rothwell
2017-01-18 0:37 Stephen Rothwell
2016-11-22 1:22 Stephen Rothwell
2016-11-22 1:28 ` Florian Fainelli
2016-11-22 8:23 ` Thomas Petazzoni
2015-06-20 13:12 Stephen Rothwell
2015-06-20 17:40 ` Florian Westphal
2015-06-20 18:31 ` Pablo Neira Ayuso
2015-05-14 7:12 Stephen Rothwell
2015-05-14 14:47 ` Willem de Bruijn
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=20170320170713.71010326@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=Chad.Dupuis@cavium.com \
--cc=Manish.Rangankar@cavium.com \
--cc=Ram.Amrani@cavium.com \
--cc=Tomer.Tayar@cavium.com \
--cc=Yuval.Mintz@cavium.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).