linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Sarah Sharp <sarah.a.sharp@linux.intel.com>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
	Yinghai Lu <yinghai@kernel.org>,
	linux-pci@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	ACPI Devel Mailing List <linux-acpi@vger.kernel.org>,
	Len Brown <lenb@kernel.org>
Subject: Re: Hot plug issue on 2.6.38
Date: Tue, 22 Mar 2011 00:41:50 +0100	[thread overview]
Message-ID: <201103220041.51154.rjw@sisk.pl> (raw)
In-Reply-To: <20110321233104.GA4334@xanatos>

On Tuesday, March 22, 2011, Sarah Sharp wrote:
> On Mon, Mar 21, 2011 at 10:34:08PM +0000, Matthew Garrett wrote:
> > Try setting CONFIG_HOTPLUG_PCI_ACPI to y as well, just to rule that out?
> 
> It's set to build as a module, do you want me to compile it in?

Yes, if poss.  But as I said before, please make sure you have the ASPM patch
applied.

Rafael

  reply	other threads:[~2011-03-21 23:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-05 21:54 [RFT][PATCH] PCI / ACPI: Do not require MSI support for PCIe native features Rafael J. Wysocki
2011-03-14 18:26 ` Sarah Sharp
2011-03-14 20:02   ` Rafael J. Wysocki
2011-03-14 20:19     ` Sarah Sharp
2011-03-14 20:37       ` Rafael J. Wysocki
2011-03-14 23:47         ` Sarah Sharp
2011-03-15  0:00           ` Rafael J. Wysocki
2011-03-15 19:05             ` Sarah Sharp
2011-03-17  0:19               ` Rafael J. Wysocki
2011-03-17  5:23                 ` Yinghai Lu
2011-03-17 21:22                   ` Rafael J. Wysocki
2011-03-17 21:56                     ` Sarah Sharp
2011-03-21 22:28                       ` Hot plug issue on 2.6.38 Sarah Sharp
2011-03-21 22:34                         ` Matthew Garrett
2011-03-21 23:31                           ` Sarah Sharp
2011-03-21 23:41                             ` Rafael J. Wysocki [this message]
2011-03-21 22:51                         ` Rafael J. Wysocki
2011-03-21 23:54                           ` Sarah Sharp
2011-03-22  0:07                             ` Rafael J. Wysocki

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=201103220041.51154.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=jbarnes@virtuousgeek.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=sarah.a.sharp@linux.intel.com \
    --cc=yinghai@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 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).