Linux-Next Archive on lore.kernel.org
 help / color / Atom feed
From: "Madhani, Himanshu" <Himanshu.Madhani@cavium.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Trapp, Darren" <Darren.Trapp@cavium.com>,
	"Grigsby, Duane" <Duane.Grigsby@cavium.com>,
	Anil Gurumurthy <anil.gurumurhty@cavium.com>,
	"Malavali, Giridhar" <Giridhar.Malavali@cavium.com>,
	Hannes Reinecke <hare@suse.com>
Subject: Re: linux-next: build warnings after merge of the scsi-mkp tree
Date: Thu, 29 Jun 2017 18:35:35 +0000
Message-ID: <F7325129-BC4E-43C1-8E33-C5C36C4BB2BF@cavium.com> (raw)
In-Reply-To: <20170629150752.4ef9a713@canb.auug.org.au>

Hi Stephen, James,

> On Jun 28, 2017, at 10:07 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> 
> Hi James,
> 
> This has now migrated to the scsi tree.
> 
> On Wed, 28 Jun 2017 15:55:10 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>> 
>> After merging the scsi-mkp tree, today's linux-next build
>> (powerpc_ppc64_defconfig) produced these warnings:
>> 
>> In file included from include/linux/byteorder/big_endian.h:4:0,
>>                 from arch/powerpc/include/uapi/asm/byteorder.h:13,
>>                 from include/asm-generic/bitops/le.h:5,
>>                 from arch/powerpc/include/asm/bitops.h:246,
>>                 from include/linux/bitops.h:36,
>>                 from include/linux/kernel.h:10,
>>                 from include/asm-generic/bug.h:15,
>>                 from arch/powerpc/include/asm/bug.h:127,
>>                 from include/linux/bug.h:4,
>>                 from arch/powerpc/include/asm/mmu.h:125,
>>                 from arch/powerpc/include/asm/lppaca.h:36,
>>                 from arch/powerpc/include/asm/paca.h:21,
>>                 from arch/powerpc/include/asm/current.h:16,
>>                 from include/linux/sched.h:11,
>>                 from include/linux/blkdev.h:4,
>>                 from include/linux/blk-mq.h:4,
>>                 from drivers/scsi/qla2xxx/qla_nvme.h:10,
>>                 from drivers/scsi/qla2xxx/qla_nvme.c:7:
>> drivers/scsi/qla2xxx/qla_nvme.c: In function 'qla2x00_start_nvme_mq':
>> 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/qla2xxx/qla_nvme.c:444:27: note: in expansion of macro 'cpu_to_le32'
>>    cont_pkt->entry_type = cpu_to_le32(CONTINUE_A64_TYPE);
>>                           ^
>> drivers/scsi/qla2xxx/qla_nvme.c: At top level:
>> drivers/scsi/qla2xxx/qla_nvme.c:667:13: warning: 'qla_nvme_unregister_remote_port' defined but not used [-Wunused-function]
>> static void qla_nvme_unregister_remote_port(struct work_struct *work)
>>             ^
>> drivers/scsi/qla2xxx/qla_nvme.c:604:12: warning: 'qla_nvme_wait_on_rport_del' defined but not used [-Wunused-function]
>> static int qla_nvme_wait_on_rport_del(fc_port_t *fcport)
>>            ^
>> drivers/scsi/qla2xxx/qla_nvme.c:634:13: warning: 'qla_nvme_abort_all' defined but not used [-Wunused-function]
>> static void qla_nvme_abort_all(fc_port_t *fcport)
>>             ^
>> 
>> Introduced by commit
>> 
>>  e84067d74301 ("scsi: qla2xxx: Add FC-NVMe F/W initialization and transport registration")
> 
> -- 
> Cheers,
> Stephen Rothwell


Would it be okay if we send patch to address this warnings in couple days? 

Thanks,
- Himanshu

  reply index

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-28  5:55 Stephen Rothwell
2017-06-29  5:07 ` Stephen Rothwell
2017-06-29 18:35   ` Madhani, Himanshu [this message]
2018-02-13  3:00 Stephen Rothwell
2021-03-03  6:03 Stephen Rothwell
2021-04-21  6:03 ` 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=F7325129-BC4E-43C1-8E33-C5C36C4BB2BF@cavium.com \
    --to=himanshu.madhani@cavium.com \
    --cc=Darren.Trapp@cavium.com \
    --cc=Duane.Grigsby@cavium.com \
    --cc=Giridhar.Malavali@cavium.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=anil.gurumurhty@cavium.com \
    --cc=hare@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=sfr@canb.auug.org.au \
    /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