From: Peter Jones <pjones@redhat.com>
To: Len Brown <lenb@kernel.org>
Cc: Konrad Rzeszutek Wilk <konrad@kernel.org>,
linux-kernel@vger.kernel.org, gpxe-devel@etherboot.org,
Peter Jones <pjones@redhat.com>
Subject: [PATCH] Use IBFT_SIGN instead of open-coding the search string.
Date: Wed, 12 May 2010 10:12:53 -0400 [thread overview]
Message-ID: <1273673573-8570-1-git-send-email-pjones@redhat.com> (raw)
In-Reply-To: <4BEAB683.8040600@redhat.com>
We define IBFT_SIGN to "iBFT"; may as well use it.
---
drivers/firmware/iscsi_ibft_find.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/firmware/iscsi_ibft_find.c b/drivers/firmware/iscsi_ibft_find.c
index 82a7a15..2192456 100644
--- a/drivers/firmware/iscsi_ibft_find.c
+++ b/drivers/firmware/iscsi_ibft_find.c
@@ -100,7 +100,7 @@ unsigned long __init find_ibft_region(unsigned long *sizep)
if (!ibft_addr)
acpi_table_parse(ACPI_SIG_IBFT, acpi_find_ibft);
if (!ibft_addr)
- acpi_table_parse("iBFT", acpi_find_ibft);
+ acpi_table_parse(IBFT_SIGN, acpi_find_ibft);
#endif /* CONFIG_ACPI */
/* iBFT 1.03 section 1.4.3.1 mandates that UEFI machines will
--
1.7.0.1
next prev parent reply other threads:[~2010-05-12 14:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-09 14:21 [PATCH] Update iBFT to 1.03 Konrad Rzeszutek Wilk
2010-04-09 14:21 ` [PATCH 1/2] ibft: Update iBFT handling for v1.03 of the spec Konrad Rzeszutek Wilk
2010-04-21 21:26 ` Andrew Morton
2010-05-11 17:58 ` Konrad Rzeszutek Wilk
2010-05-12 5:26 ` Len Brown
2010-05-12 13:58 ` [LKML] " Konrad Rzeszutek Wilk
2010-05-12 14:09 ` Peter Jones
2010-05-12 14:12 ` Peter Jones [this message]
2010-05-12 14:25 ` [PATCH] Use IBFT_SIGN instead of open-coding the search string Peter Jones
2010-05-12 14:35 ` [PATCH] ibft: " Konrad Rzeszutek Wilk
2010-05-12 19:33 ` Andrew Morton
2010-05-12 23:53 ` H. Peter Anvin
2010-05-27 17:59 ` Konrad Rzeszutek Wilk
2010-04-09 14:21 ` [PATCH 2/2] ibft: For UEFI machines actually do scan ACPI for iBFT Konrad Rzeszutek Wilk
2010-04-21 21:29 ` Andrew Morton
2010-04-21 21:37 ` Mike Christie
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=1273673573-8570-1-git-send-email-pjones@redhat.com \
--to=pjones@redhat.com \
--cc=gpxe-devel@etherboot.org \
--cc=konrad@kernel.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@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).