From: Matt Fleming <matt.fleming@intel.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Matt Fleming <matt@console-pimps.org>,
Matthew Garrett <mjg59@srcf.ucam.org>,
linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/6] Chainsaw efivars.c
Date: Tue, 09 Apr 2013 17:50:15 +0100 [thread overview]
Message-ID: <516446C7.8080802@intel.com> (raw)
In-Reply-To: <516440F5.7040904@zytor.com>
On 09/04/13 17:25, H. Peter Anvin wrote:
> On 04/04/2013 05:18 AM, Matt Fleming wrote:
>> From: Matt Fleming <matt.fleming@intel.com>
>>
>> drivers/firmware/efivars.c has grown pretty large and is ~2K lines.
>>
>
> Hi Matt,
>
> Are you expecting me or Matt G. to take this one?
I was going to send it to you in a pull request once it had been
reviewed. It's a pretty invasive change and I was trying to avoid
breaking drivers/firmware/google in particular. I don't think it's
suitable for merging for v3.10, unless Mike and the pstore folks are
happy with it (and make it known fairly soon).
prev parent reply other threads:[~2013-04-09 16:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 12:18 [PATCH 0/6] Chainsaw efivars.c Matt Fleming
2013-04-04 12:18 ` [PATCH 1/6] efi: move utf16 string functions to efi.h Matt Fleming
2013-04-09 22:00 ` Mike Waychison
2013-04-10 11:18 ` David Woodhouse
2013-04-04 12:18 ` [PATCH 2/6] efivars: Keep a private global pointer to efivars Matt Fleming
2013-04-09 22:07 ` Mike Waychison
2013-04-11 13:10 ` Matt Fleming
2013-04-04 12:18 ` [PATCH 3/6] efivars: efivar_entry API Matt Fleming
2013-04-10 15:25 ` Seiji Aguchi
2013-04-11 13:34 ` Matt Fleming
2013-04-04 12:18 ` [PATCH 4/6] efivars: Move pstore code into the new EFI directory Matt Fleming
2013-04-04 12:18 ` [PATCH 5/6] efivarfs: Move to fs/efivarfs Matt Fleming
2013-04-04 12:18 ` [PATCH 6/6] efi: split efisubsystem from efivars Matt Fleming
2013-04-09 16:25 ` [PATCH 0/6] Chainsaw efivars.c H. Peter Anvin
2013-04-09 16:50 ` Matt Fleming [this message]
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=516446C7.8080802@intel.com \
--to=matt.fleming@intel.com \
--cc=hpa@zytor.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@console-pimps.org \
--cc=mjg59@srcf.ucam.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