From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Alan Stern <stern@rowland.harvard.edu>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the scsi tree
Date: Wed, 04 Aug 2010 00:17:56 -0400 [thread overview]
Message-ID: <1280895476.11045.323.camel@mulgrave.site> (raw)
In-Reply-To: <20100804131300.8570fe77.sfr@canb.auug.org.au>
cc linux-scsi added
On Wed, 2010-08-04 at 13:13 +1000, Stephen Rothwell wrote:
> Hi James,
>
> After merging the scsi tree, today's linux-next build (powerpc
> ppc64_defconfig) produced this warning:
>
> drivers/scsi/scsi_sysfs.c:384: warning: dereferencing 'void *' pointer
>
> Introduced by commit db5bd1e0b505c54ff492172ce4abc245cf6cd639 ("[SCSI]
> convert to the new PM framework"). This build does not have
> CONFIG_PM_OPS set.
So this one looks to be a compiler error. in the none CONFIG_PM_OPS
case, we have
scsi_priv.h:#define scsi_bus_pm_ops (*NULL)
So &scsi_bus_pm_ops should be NULL (not a deref of null).
James
parent reply other threads:[~2010-08-04 4:17 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20100804131300.8570fe77.sfr@canb.auug.org.au>]
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=1280895476.11045.323.camel@mulgrave.site \
--to=james.bottomley@hansenpartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=stern@rowland.harvard.edu \
/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).