From: Colin Walters <walters@verbum.org>
To: joeyli <jlee@suse.com>
Cc: Matt Fleming <matt.fleming@intel.com>,
systemd-devel@lists.freedesktop.org, Kay Sievers <kay@vrfy.org>,
linux-efi@vger.kernel.org,
Jeremy Kerr <jeremy.kerr@canonical.com>,
Matthew Garrett <mjg@redhat.com>
Subject: Re: [PATCH] systemd: mount the EFI variable filesystem
Date: Wed, 31 Oct 2012 09:04:30 -0400 [thread overview]
Message-ID: <1351688670.9230.4.camel@lenny> (raw)
In-Reply-To: <1351477290.21227.7.camel@linux-s257.site>
On Mon, 2012-10-29 at 10:21 +0800, joeyli wrote:
> I tested this patch on my UEFI notebook with latest EFI kernel git tree,
> the efivarfs mounted normally after system boot and I can delete/add EFI
> variable through /sys/firmware/efi/efivars.
This causes systemd to output a warning if the kernel doesn't have an
efivars module. I suppose to do this kind of thing "right" we'd
have to conditionalize the module loads on available kernel version they
first appeared in?
(Yes, I frequently I boot bleeding edge systemd from git on older
kernels)
next prev parent reply other threads:[~2012-10-31 13:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-27 3:23 [PATCH] systemd: mount the EFI variable filesystem Lee, Chun-Yi
[not found] ` <1351308202-14628-1-git-send-email-jlee-IBi9RG/b67k@public.gmane.org>
2012-10-28 13:00 ` Lennart Poettering
[not found] ` <20121028130025.GD7904-kS5D54t9nk0aINubkmmoJbNAH6kLmebB@public.gmane.org>
2012-10-29 2:21 ` joeyli
2012-10-31 13:04 ` Colin Walters [this message]
2012-10-31 13:13 ` [systemd-devel] " Kay Sievers
[not found] ` <CAPXgP10j+AGUcyaimtp=osb9mVVpPNJqCvsOdENWhPQEmfYC3A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-11-05 20:55 ` Josh Boyer
-- strict thread matches above, loose matches on Subject: below --
2012-10-25 8:23 Lee, Chun-Yi
2012-10-25 8:07 Lee, Chun-Yi
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=1351688670.9230.4.camel@lenny \
--to=walters@verbum.org \
--cc=jeremy.kerr@canonical.com \
--cc=jlee@suse.com \
--cc=kay@vrfy.org \
--cc=linux-efi@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=mjg@redhat.com \
--cc=systemd-devel@lists.freedesktop.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 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.