From: "H. Peter Anvin" <hpa@zytor.com>
To: joeyli <jlee@suse.com>
Cc: Peter Jones <pjones@redhat.com>,
jeremy.kerr@canonical.com, Matthew Garrett <mjg@redhat.com>,
linux-kernel@vger.kernel.org, Matt Domsch <Matt_Domsch@Dell.com>,
glin@suse.com
Subject: Re: [RFC,PATCH v2] efi: Add support for a UEFI variable filesystem
Date: Thu, 13 Sep 2012 21:41:26 -0700 [thread overview]
Message-ID: <5052B576.8010500@zytor.com> (raw)
In-Reply-To: <1347594342.705.33.camel@linux-s257.site>
On 09/13/2012 08:45 PM, joeyli wrote:
> Hi Peter,
>
> 於 四，2012-09-13 於 09:52 -0400，Peter Jones 提到：
>> On Thu, 2012-09-13 at 16:10 +0800, joeyli wrote:
>>
>>> Do we have plan to create a new kobject add to /sys/firmware/efi for
>>> provide a fixed mount point to efivars fs?
>>> e.g. /sys/firmware/efi/efivars
>>>
>>> Or we just direct reuse current /sys/firmeware/efi/vars? But, that means
>>> we need think for the backward compatibility if choice reuse vars
>>> folder.
>>
>> I'm not sure that's a terribly large concern - if you haven't updated
>> your tools to use the new efivars, don't mount the new efivars.
>>
>
> Thanks for your comment!
>
I think it is wrong. The new API should have a different path.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2012-09-14 4:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 5:40 [RFC,PATCH v2] efi: Add support for a UEFI variable filesystem Jeremy Kerr
2012-09-06 14:18 ` Matt Fleming
2012-09-06 14:23 ` Jeremy Kerr
2012-09-06 14:30 ` Matt Fleming
2012-09-06 14:37 ` Jeremy Kerr
2012-09-06 14:46 ` Matt Fleming
[not found] ` <CAGLnvc9BXAW8F8WWyDxuF1_J+0np3uqUBmknuJewOJHhe-mxvw@mail.gmail.com>
2012-09-13 8:08 ` Fwd: " joeyli
2012-09-13 8:10 ` joeyli
2012-09-13 13:52 ` Peter Jones
2012-09-14 3:45 ` joeyli
2012-09-14 4:41 ` H. Peter Anvin [this message]
2012-09-15 2:44 ` joeyli
2012-09-15 2:26 ` joeyli
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=5052B576.8010500@zytor.com \
--to=hpa@zytor.com \
--cc=Matt_Domsch@Dell.com \
--cc=glin@suse.com \
--cc=jeremy.kerr@canonical.com \
--cc=jlee@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg@redhat.com \
--cc=pjones@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.