All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@mbligh.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: bill@crowellsystems.com
Subject: [Bug 6537] New: #ifdef CONFIG_PM causes MPT to not compile
Date: Fri, 12 May 2006 07:58:54 -0700	[thread overview]
Message-ID: <4464A2AE.9080905@mbligh.org> (raw)


http://bugzilla.kernel.org/show_bug.cgi?id=6537

            Summary: #ifdef CONFIG_PM causes MPT to not compile
     Kernel Version: 2.6.17-rc4
             Status: NEW
           Severity: blocking
              Owner: io_other@kernel-bugs.osdl.org
          Submitter: bill@crowellsystems.com


Most recent kernel where this bug did not occur: 2.6.17-rc3
Distribution: slack
Hardware Environment: i386
Software Environment: gcc 3.3
Problem Description: /drivers/message/fusion/mpt* using #ifdef CONFIG_PM 
are not
exporting the mpt_suspend mpt_resume. I do not know why we would want to
exercise power management on high-performance scsi controllers in the first
place. LSI controllers are server devices.

Steps to reproduce: compile the kernel. causes a kernel compilation failure.

Steps to fix:
comment out the #ifdef CONFIG_pm and corresponding #endif to disable this
compilation flag. recompile and the world is happy.


             reply	other threads:[~2006-05-12 14:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-12 14:58 Martin J. Bligh [this message]
2006-05-12 16:45 ` [Bug 6537] New: #ifdef CONFIG_PM causes MPT to not compile Alexey Dobriyan
  -- strict thread matches above, loose matches on Subject: below --
2006-05-12 22:10 Moore, Eric

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=4464A2AE.9080905@mbligh.org \
    --to=mbligh@mbligh.org \
    --cc=bill@crowellsystems.com \
    --cc=linux-kernel@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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.