From: Jesse Barnes <jbarnes@virtuousgeek•org>
To: "Rafael J. Wysocki" <rjw@sisk•pl>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: linux-next: build failure after merge of the final tree (pci-current tree related)
Date: Wed, 25 Aug 2010 12:54:20 -0700 [thread overview]
Message-ID: <20100825125420.78d63e37@virtuousgeek.org> (raw)
In-Reply-To: <201008252133.29525.rjw@sisk.pl>
On Wed, 25 Aug 2010 21:33:29 +0200
"Rafael J. Wysocki" <rjw@sisk•pl> wrote:
> Subject: PCI / hot-plug: Fix build with CONFIG_ACPI unset
>
> One of the recent changes caused complilation of
> drivers/pci/hotplug/pciehp_core.c to fail. Fix this issue.
>
> Signed-off-by: Rafael J. Wysocki <rjw@sisk•pl>
Fix pushed out to my for-linus branch, thanks guys.
--
Jesse Barnes, Intel Open Source Technology Center
prev parent reply other threads:[~2010-08-25 19:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 1:56 linux-next: build failure after merge of the final tree (pci-current tree related) Stephen Rothwell
2010-08-25 19:33 ` Rafael J. Wysocki
2010-08-25 19:54 ` Jesse Barnes [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=20100825125420.78d63e37@virtuousgeek.org \
--to=jbarnes@virtuousgeek$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rjw@sisk$(echo .)pl \
--cc=sfr@canb$(echo .)auug.org.au \
/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