From: Matt Domsch <Matt_Domsch@dell.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: gregkh@suse.de, Dave Jiang <dave.jiang@intel.com>,
linux-scsi@vger.kernel.org, jacek.danecki@intel.com,
ed.ciechanowski@intel.com, linux-kernel@vger.kernel.org,
dmilburn@redhat.com, edmund.nadolski@intel.com,
Mike Waychison <mikew@google.com>
Subject: Re: [PATCH] firmware/efi: export a routine to retrieve efi-variables by GUID
Date: Mon, 21 Mar 2011 22:49:37 -0500 [thread overview]
Message-ID: <20110322034937.GA20235@auslistsprd01.us.dell.com> (raw)
In-Reply-To: <20110318221606.26841.92271.stgit@localhost6.localdomain6>
On Fri, Mar 18, 2011 at 03:16:22PM -0700, Dan Williams wrote:
> From: Dave Jiang <dave.jiang@intel.com>
>
> The efivars module already scans all available variables, normalizes the
> variable names, and stores them in a list. Rather than duplicate this
> to efi runtime services interface let drivers query variable data by
> GUID.
Mike Waychison made a lot of good edits to the driver which are staged
for .39 in gregkh's tree. Some of those changes will conflict with
your patch here, specifically the definition of struct efi_variable
moved similar to what you have done here.
You'll want to rebase your changes accordingly.
Thanks,
Matt
--
Matt Domsch
Technology Strategist
Dell | Office of the CTO
prev parent reply other threads:[~2011-03-22 3:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 22:16 [PATCH] firmware/efi: export a routine to retrieve efi-variables by GUID Dan Williams
2011-03-18 22:50 ` Greg KH
2011-03-18 23:10 ` Dan Williams
2011-03-19 0:22 ` Greg KH
2011-03-19 1:15 ` Dan Williams
2011-03-20 0:14 ` Greg KH
2011-03-20 1:13 ` James Bottomley
2011-03-21 19:07 ` Dan Williams
2011-03-21 19:12 ` Christoph Hellwig
2011-03-21 18:41 ` Dan Williams
2011-03-22 3:49 ` Matt Domsch [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=20110322034937.GA20235@auslistsprd01.us.dell.com \
--to=matt_domsch@dell.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dmilburn@redhat.com \
--cc=ed.ciechanowski@intel.com \
--cc=edmund.nadolski@intel.com \
--cc=gregkh@suse.de \
--cc=jacek.danecki@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mikew@google.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).