From: "H. Peter Anvin" <hpa@zytor.com>
To: Dave Young <dyoung@redhat.com>, matt@console-pimps.org
Cc: greg@kroah.com, linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org
Subject: Re: split efi systab in sysfs
Date: Wed, 25 Dec 2013 17:55:27 -0800 [thread overview]
Message-ID: <52BB8C8F.1020606@zytor.com> (raw)
In-Reply-To: <20131226015308.GA3750@dhcp-16-126.nay.redhat.com>
On 12/25/2013 05:53 PM, Dave Young wrote:
> Hi, Matt and Peter
>
> Currently /sys/firmware/efi/systab contains multi-lines for efi systab
> entries. As previous discussion with Greg, this is not a good in sysfs.
> I wonder if there's other users for this file except kexec-tools.
>
> If kexec-tools is the only user, maybe I can split it as several files.
> In kexec-tools just use /sys/firmware/efi/"$entry_name" and if $entry_name
> does not exist then switch to old systab file.
>
Yes, the sysfs standard is "one entry per datum". I have no idea about
who the user(s) might be, though.
-hpa
next prev parent reply other threads:[~2013-12-26 1:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-26 1:53 split efi systab in sysfs Dave Young
2013-12-26 1:55 ` H. Peter Anvin [this message]
2013-12-26 2:12 ` Dave Young
2013-12-26 2:17 ` Dave Young
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=52BB8C8F.1020606@zytor.com \
--to=hpa@zytor.com \
--cc=dyoung@redhat.com \
--cc=greg@kroah.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@console-pimps.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