From: Stephen Rothwell <sfr@canb•auug.org.au>
To: James Bottomley <James.Bottomley@HansenPartnership•com>
Cc: Linux-Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Johannes Thumshirn <jthumshirn@suse•de>,
"Martin K. Petersen" <martin.petersen@oracle•com>,
Hannes Reinecke <hare@suse•com>
Subject: Re: linux-next: build warnings after merge of the scsi tree
Date: Mon, 11 Dec 2017 15:26:37 +1100 [thread overview]
Message-ID: <20171211152637.2d566a8d@canb.auug.org.au> (raw)
In-Reply-To: <20171206133149.30baf3eb@canb.auug.org.au>
Hi all,
On Wed, 6 Dec 2017 13:31:49 +1100 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> After merging the scsi tree, today's linux-next build (x86_64
> allmodconfig) produced these warnings:
>
> drivers/scsi/bfa/bfad_bsg.c: In function 'bfad_im_bsg_vendor_request':
> drivers/scsi/bfa/bfad_bsg.c:3137:35: warning: initialization makes pointer from integer without a cast [-Wint-conversion]
> struct bfad_im_port_s *im_port = shost->hostdata[0];
> ^
> drivers/scsi/bfa/bfad_bsg.c: In function 'bfad_im_bsg_els_ct_request':
> drivers/scsi/bfa/bfad_bsg.c:3353:35: warning: initialization makes pointer from integer without a cast [-Wint-conversion]
> struct bfad_im_port_s *im_port = shost->hostdata[0];
> ^
>
> Introduced by commit
>
> 45349821ab3a ("scsi: bfa: fix access to bfad_im_port_s")
I am still getting these ...
--
Cheers,
Stephen Rothwell
prev parent reply other threads:[~2017-12-11 4:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 2:31 linux-next: build warnings after merge of the scsi tree Stephen Rothwell
2017-12-11 4:26 ` Stephen Rothwell [this message]
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=20171211152637.2d566a8d@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=James.Bottomley@HansenPartnership$(echo .)com \
--cc=hare@suse$(echo .)com \
--cc=jthumshirn@suse$(echo .)de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=martin.petersen@oracle$(echo .)com \
/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