From: Christoph Hellwig <hch@infradead.org>
To: Dan Williams <dan.j.williams@intel.com>
Cc: James Bottomley <James.Bottomley@suse.de>,
Greg KH <gregkh@suse.de>, "Jiang, Dave" <dave.jiang@intel.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"Danecki, Jacek" <jacek.danecki@intel.com>,
"Ciechanowski, Ed" <ed.ciechanowski@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dmilburn@redhat.com" <dmilburn@redhat.com>,
"Nadolski, Edmund" <edmund.nadolski@intel.com>,
Jeff Garzik <jeff@garzik.org>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH] firmware/efi: export a routine to retrieve efi-variables by GUID
Date: Mon, 21 Mar 2011 15:12:19 -0400 [thread overview]
Message-ID: <20110321191219.GA6761@infradead.org> (raw)
In-Reply-To: <4D87A1E6.2000006@intel.com>
On Mon, Mar 21, 2011 at 12:07:18PM -0700, Dan Williams wrote:
> Ideally this would have been something that just showed up in an
> option-rom bar on the device, but that did not happen so it is left
> to software. For legacy-bios we scan adapter rom space looking for
> our table, for efi it's comparatively cleaner we just grab this efi
> variable identified by its own GUID.
In the worse case a late merged icsi driver just wouldn't support
EFI-based boards out ot the box until 2.6.40. I don't think that
is too much of an issue.
next prev parent reply other threads:[~2011-03-21 19:12 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 [this message]
2011-03-21 18:41 ` Dan Williams
2011-03-22 3:49 ` Matt Domsch
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=20110321191219.GA6761@infradead.org \
--to=hch@infradead.org \
--cc=James.Bottomley@suse.de \
--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=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).