From: Huang Ying <ying.huang@intel.com>
To: Len Brown <lenb@kernel.org>, Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: linux-kernel@vger.kernel.org, Andi Kleen <ak@linux.intel.com>,
linux-acpi@vger.kernel.org, linux-pci@vger.kernel.org
Subject: [PATCH -v2 0/2] ACPI, APEI, use general HEST table parsing in AER firmware_first setup (resend)
Date: Thu, 11 Mar 2010 10:14:56 +0800 [thread overview]
Message-ID: <1268273698-21940-1-git-send-email-ying.huang@intel.com> (raw)
Changelog:
v2:
- Setup firmware_first for every PCIE end point instead of just root point.
- Wrap firmware accessing in a function instead of raw hardware, because HEST
parsing involved.
next reply other threads:[~2010-03-11 2:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 2:14 Huang Ying [this message]
2010-03-11 2:14 ` [PATCH -v2 1/2] ACPI, APEI, Make APEI core configurable built-in instead of module Huang Ying
2010-03-11 2:14 ` [PATCH -v2 2/2] ACPI, APEI, PCIE AER, use general HEST table parsing in AER firmware_first setup Huang Ying
2010-03-12 3:43 ` Hidetoshi Seto
2010-03-12 7:59 ` Huang Ying
2010-03-13 1:23 ` Jesse Barnes
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=1268273698-21940-1-git-send-email-ying.huang@intel.com \
--to=ying.huang@intel.com \
--cc=ak@linux.intel.com \
--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 \
/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