linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: joeyli <jlee@suse.com>
To: Peter Jones <pjones@redhat.com>
Cc: jeremy.kerr@canonical.com, Matthew Garrett <mjg@redhat.com>,
	linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
	Matt Domsch <Matt_Domsch@Dell.com>,
	glin@suse.com
Subject: Re: [RFC,PATCH v2] efi: Add support for a UEFI variable filesystem
Date: Fri, 14 Sep 2012 11:45:42 +0800	[thread overview]
Message-ID: <1347594342.705.33.camel@linux-s257.site> (raw)
In-Reply-To: <1347544333.6707.1.camel@eddie.install.bos.redhat.com>

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!

Joey Lee


  reply	other threads:[~2012-09-14  3:51 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 [this message]
2012-09-14  4:41         ` H. Peter Anvin
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=1347594342.705.33.camel@linux-s257.site \
    --to=jlee@suse.com \
    --cc=Matt_Domsch@Dell.com \
    --cc=glin@suse.com \
    --cc=hpa@zytor.com \
    --cc=jeremy.kerr@canonical.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 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).