Linux-Next Archive on lore.kernel.org
 help / color / Atom feed
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
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

             reply index

Thread overview: 11+ 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 --
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 publically 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

Linux-Next Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-next/0 linux-next/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-next linux-next/ https://lore.kernel.org/linux-next \
		linux-next@vger.kernel.org
	public-inbox-index linux-next

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-next


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git