From: "Luck, Tony" <tony.luck@intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Punit Agrawal <punit.agrawal@arm.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>, Boris Petkov <bp@suse.de>,
Tyler Baicar <tbaicar@codeaurora.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ACPI/APEI: Add BERT data driver
Date: Thu, 17 Aug 2017 13:29:55 -0700 [thread overview]
Message-ID: <20170817202954.v7v6eoh7vdearxlx@intel.com> (raw)
In-Reply-To: <CAJZ5v0hgnbR7AbObAYDEYRpG-WjgW-qd=Qieh5a4XLa=ZGpxTg@mail.gmail.com>
On Thu, Aug 17, 2017 at 09:28:53PM +0200, Rafael J. Wysocki wrote:
> What about /sys/firmware/acpi/tables/data/ and then one file per table
> under it with the same name as the table file under tables/ ?
"data" works. ACPI table names are all upper-case, so it
can't conflict. Any programs that scan the whole directory
have to already skip "dynamic", so they likely would not
be confused by the appearance of a second directory.
For BERT there is only one blob of data. So naming it the
same as the table is fine. Maybe other tables might have
more than one thing? If so, they could use the table name
as a prefix, or make a subdirectory. We can cross that
bridge if anyone finds additional useful things to add.
> So in particular for BERT the data would be in
> /sys/firmware/acpi/tables/data/BERT ?
Ok. Will re-spin the patch with these names.
-Tony
next prev parent reply other threads:[~2017-08-17 20:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-14 16:56 [PATCH] ACPI/APEI: Add BERT data driver Luck, Tony
2017-08-15 10:22 ` Punit Agrawal
2017-08-15 21:15 ` Luck, Tony
2017-08-16 13:14 ` Punit Agrawal
2017-08-16 15:22 ` Luck, Tony
2017-08-17 10:25 ` Punit Agrawal
2017-08-17 17:49 ` Luck, Tony
2017-08-17 19:28 ` Rafael J. Wysocki
2017-08-17 20:29 ` Luck, Tony [this message]
2017-08-17 20:41 ` Rafael J. Wysocki
2017-08-17 21:39 ` [PATCH] ACPI / sysfs: Extend ACPI sysfs to provide access to boot error region Luck, Tony
2017-08-18 0:30 ` Alan Cox
2017-08-18 2:12 ` Luck, Tony
2017-08-23 14:56 ` Luck, Tony
2017-08-29 0:10 ` Kees Cook
2017-08-29 15:55 ` Luck, Tony
2017-08-18 17:38 ` Punit Agrawal
2017-08-18 23:19 ` [PATCH v4] " Luck, Tony
2017-08-28 20:55 ` 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=20170817202954.v7v6eoh7vdearxlx@intel.com \
--to=tony.luck@intel.com \
--cc=bp@suse.de \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=punit.agrawal@arm.com \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=tbaicar@codeaurora.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).