From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: unlisted-recipients:; (no To-header on input)
Cc: Yinghai Lu <yhlu.kernel@gmail.com>,
Matt Domsch <Matt_Domsch@dell.com>,
Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>,
linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org,
Tom Long Nguyen <tom.l.nguyen@intel.com>,
Zhang Yanmin <yanmin.zhang@intel.com>,
linux-kernel@vger.kernel.org,
Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>,
Huong_Nguyen@dell.com
Subject: Re: [PATCH] PCIe AER: honor ACPI HEST FIRMWARE FIRST mode
Date: Wed, 4 Nov 2009 13:07:49 -0800 [thread overview]
Message-ID: <20091104130749.0686210d@jbarnes-piketon> (raw)
In-Reply-To: <20091104130515.6ffb0e2b@jbarnes-piketon>
On Wed, 4 Nov 2009 13:05:15 -0800
Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> > can not find acpi_hest.c and acpi_hest.h
> >
> > maybe need to wait acpi hest code is there?
>
> Arg, when I fixed up a conflict in the patch I forgot to add those
> files to the commit. They were in my tree so I didn't see a build
> error... Fixing now.
Should be all fixed now, thanks for catching it Yinghai.
--
Jesse Barnes, Intel Open Source Technology Center
prev parent reply other threads:[~2009-11-04 21:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 17:33 Matt Domsch
2009-10-08 0:59 ` Hidetoshi Seto
[not found] ` <851fc09e0910082221q7f832c22xfc0d01ab72a97c3f@mail.gmail.com>
2009-10-09 5:55 ` Fwd: " Huang Ying
2009-10-09 14:31 ` Matt Domsch
2009-10-09 7:11 ` Kenji Kaneshige
2009-10-09 18:28 ` Matt Domsch
2009-10-09 18:33 ` Matt Domsch
2009-10-29 14:15 ` Matt Domsch
2009-10-29 16:48 ` Jesse Barnes
2009-10-30 2:16 ` Hidetoshi Seto
2009-10-30 2:53 ` Matt Domsch
2009-10-30 3:24 ` Hidetoshi Seto
2009-11-02 17:51 ` Matt Domsch
2009-11-04 17:11 ` Jesse Barnes
2009-11-04 20:55 ` Yinghai Lu
2009-11-04 21:05 ` Jesse Barnes
2009-11-04 21:07 ` 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=20091104130749.0686210d@jbarnes-piketon \
--to=jbarnes@virtuousgeek.org \
--cc=Huong_Nguyen@dell.com \
--cc=Matt_Domsch@dell.com \
--cc=kaneshige.kenji@jp.fujitsu.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=seto.hidetoshi@jp.fujitsu.com \
--cc=tom.l.nguyen@intel.com \
--cc=yanmin.zhang@intel.com \
--cc=yhlu.kernel@gmail.com \
/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
all inboxes | Powered by JetHome®