From: "Luck, Tony" <tony.luck@intel.com>
To: Jeshua Smith <jeshuas@nvidia.com>,
"keescook@chromium.org" <keescook@chromium.org>,
"gpiccoli@igalia.com" <gpiccoli@igalia.com>,
"rafael@kernel.org" <rafael@kernel.org>,
"lenb@kernel.org" <lenb@kernel.org>,
"james.morse@arm.com" <james.morse@arm.com>,
"bp@alien8.de" <bp@alien8.de>
Cc: "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-hardening@vger.kernel.org"
<linux-hardening@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
Thierry Reding <treding@nvidia.com>,
Jonathan Hunter <jonathanh@nvidia.com>
Subject: RE: [PATCH V2] ACPI: APEI: Use ERST timeout for slow devices
Date: Fri, 4 Aug 2023 16:31:21 +0000 [thread overview]
Message-ID: <SJ1PR11MB6083426D3C663F47E707CF1AFC09A@SJ1PR11MB6083.namprd11.prod.outlook.com> (raw)
In-Reply-To: <DM6PR12MB3371BA50E3B76D2266273901DB09A@DM6PR12MB3371.namprd12.prod.outlook.com>
> Can the maintainers please respond to my patch?
Can you give a reference to the ACPI spec where this timing information is documented? I'm looking at ACPI 6.5
and don't see anything about this.
https://uefi.org/specs/ACPI/6.5/18_Platform_Error_Interfaces.html#error-serialization
-Tony
next prev parent reply other threads:[~2023-08-04 16:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 22:34 [PATCH V2] ACPI: APEI: Use ERST timeout for slow devices Jeshua Smith
2023-08-04 15:55 ` Jeshua Smith
2023-08-04 16:31 ` Luck, Tony [this message]
2023-08-05 1:04 ` Jeshua Smith
2023-08-18 16:50 ` Jeshua Smith
2023-09-11 16:15 ` Jeshua Smith
2023-10-02 16:10 ` Jeshua Smith
2023-10-23 15:45 ` Jeshua Smith
2023-10-24 14:32 ` Rafael J. Wysocki
2023-10-24 15:27 ` Borislav Petkov
2023-10-25 14:09 ` Jeshua Smith
2023-10-25 14:22 ` Borislav Petkov
2023-10-24 15:24 ` Tony Luck
2023-10-24 18:51 ` 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=SJ1PR11MB6083426D3C663F47E707CF1AFC09A@SJ1PR11MB6083.namprd11.prod.outlook.com \
--to=tony.luck@intel.com \
--cc=bp@alien8.de \
--cc=gpiccoli@igalia.com \
--cc=james.morse@arm.com \
--cc=jeshuas@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=keescook@chromium.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=treding@nvidia.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;
as well as URLs for NNTP newsgroup(s).