From: Matt Fleming <matt@console-pimps.org>
To: Tom Gundersen <teg@jklm.no>
Cc: "linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Matt Fleming <matt.fleming@intel.com>
Subject: Re: [PATCH v2 0/6] Chainsaw efivars.c
Date: Wed, 17 Apr 2013 13:48:17 +0100 [thread overview]
Message-ID: <516E9A11.1040404@console-pimps.org> (raw)
In-Reply-To: <CAG-2HqVBiSMp648F=zdUBDWQ49_a=rEPJ_TH__zWtaPSjju-KQ@mail.gmail.com>
On 04/17/2013 01:30 AM, Tom Gundersen wrote:
> Hi Matt,
>
> On Tue, Apr 16, 2013 at 11:41 PM, Matt Fleming <matt@console-pimps.org> wrote:
>> This patch series introduces the new efivar_entry API, and splits out the major
>> parts of efivars.c into new files. In particular, having the efivarfs code
>> under fs/ allows building an efivarfs.ko module, which means mount(8) can
>> automatically load it.
>>
>> The remaining EFI code is repositioned under drivers/firmware/efi/.
>
> These all look good to me, so feel free to add my Reviewed-by.
>
> Tested on top of 3.9-rc7, with everything built as modules. Everything
> works as intended: systemd correctly detects it is on an EFI system,
> so mounts efivarfs, which auto-loads the required modules.
>
> Thanks a lot!
Thanks for reviewing and testing! I've added your Reviewed-by and
Tested-by tags to all 5 patches (but not the one you authored). I found
a bug in PATCH 3, so I've sent out a v3 of the series.
Peter, I've pulled these 6 patches into the 'chainsaw' branch in the EFI
repo. I think the prudent thing to do (as you previously suggested) is
to merge that branch into tip as a separate topic branch, just in case
we need to drop it before the merge window opens.
--
Matt Fleming, Intel Open Source Technology Center
next prev parent reply other threads:[~2013-04-17 12:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 21:41 [PATCH v2 0/6] Chainsaw efivars.c Matt Fleming
2013-04-16 21:41 ` Matt Fleming
2013-04-16 21:41 ` [PATCH v2 2/6] efivars: Keep a private global pointer to efivars Matt Fleming
2013-04-16 21:41 ` [PATCH v2 3/6] efivars: efivar_entry API Matt Fleming
[not found] ` <1366148520-29954-1-git-send-email-matt-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
2013-04-16 21:41 ` [PATCH v2 1/6] efi: move utf16 string functions to efi.h Matt Fleming
2013-04-16 21:41 ` Matt Fleming
2013-04-16 21:41 ` [PATCH 4/6] efivars: Move pstore code into the new EFI directory Matt Fleming
2013-04-16 21:41 ` Matt Fleming
2013-04-16 21:41 ` [PATCH 5/6] efivarfs: Move to fs/efivarfs Matt Fleming
2013-04-16 21:41 ` Matt Fleming
2013-04-17 0:30 ` [PATCH v2 0/6] Chainsaw efivars.c Tom Gundersen
2013-04-17 0:30 ` Tom Gundersen
2013-04-17 12:48 ` Matt Fleming [this message]
2013-04-16 21:42 ` [PATCH 6/6] efi: split efisubsystem from efivars Matt Fleming
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=516E9A11.1040404@console-pimps.org \
--to=matt@console-pimps.org \
--cc=hpa@zytor.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=teg@jklm.no \
/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.