From: "Williams, Dan J" <dan.j.williams@intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build warning after merge of the final tree
Date: Wed, 28 Mar 2012 00:59:36 -0700 [thread overview]
Message-ID: <CABE8wwtqSC01O+DsjQp5U0shQh99e0vctHqRRY8e4OfxD+TaxA@mail.gmail.com> (raw)
In-Reply-To: <20120326151147.30727745f5a3410d87f391dc@canb.auug.org.au>
On Sun, Mar 25, 2012 at 9:11 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> After merging the final tree, today's linux-next build (sparc32 defconfig)
> produced these warnings (and many similar):
>
> In file included from drivers/scsi/hosts.c:41:0:
> drivers/scsi/scsi_priv.h:166:1: warning: "__enabled_CONFIG_PM" is not defined [-Wundef]
> drivers/scsi/scsi_priv.h:166:1: warning: "__enabled_CONFIG_PM_MODULE" is not defined [-Wundef]
>
> Introduced by commit a6a95fad44f1 ("scsi, sd: limit the scope of the
> async probe domain").
So, sparc does not source kernel/power/Kconfig or define config PM
locally. Compiling out this list_head (scsi_sd_probe_domain) in the
!PM && !BLK_DEV_SD case may be more trouble then it is worth. I'll
re-spin the patch without the IS_ENABLED conditionals.
--
Dan
next prev parent reply other threads:[~2012-03-28 7:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 4:11 linux-next: build warning after merge of the final tree Stephen Rothwell
2012-03-28 7:59 ` Williams, Dan J [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-05-29 5:29 Stephen Rothwell
2013-05-29 5:44 ` David Miller
2013-04-19 8:07 Stephen Rothwell
2013-04-19 9:44 ` Joerg Roedel
2012-12-17 3:22 Stephen Rothwell
2012-12-17 3:34 ` Stephen Rothwell
2012-12-17 20:59 ` Andrew Morton
2012-08-02 4:04 Stephen Rothwell
2012-08-02 14:45 ` Nathan Zimmer
2011-08-16 5:22 Stephen Rothwell
2011-08-16 6:04 ` Herbert Xu
2011-08-16 7:03 ` Stephen Rothwell
2011-08-16 7:08 ` Herbert Xu
2011-07-22 6:24 Stephen Rothwell
2011-07-22 6:26 ` David Miller
2010-09-29 4:02 Stephen Rothwell
2010-09-16 5:05 Stephen Rothwell
2010-09-16 6:29 ` Jens Axboe
2010-05-26 5:15 Stephen Rothwell
2010-03-01 8:14 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=CABE8wwtqSC01O+DsjQp5U0shQh99e0vctHqRRY8e4OfxD+TaxA@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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
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).