linux-kernel - Re: [PATCH] ibft: Use IBFT_SIGN instead of open-coding the search string.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <201005271359.59974.konrad@darnok.org>
Date:	Thu, 27 May 2010 13:59:59 -0400
From:	Konrad Rzeszutek Wilk <konrad@...nok.org>
To:	Peter Jones <pjones@...hat.com>
Cc:	Len Brown <lenb@...nel.org>,
	Konrad Rzeszutek Wilk <konrad@...nel.org>,
	linux-kernel@...r.kernel.org, gpxe-devel@...erboot.org
Subject: Re: [PATCH] ibft: Use IBFT_SIGN instead of open-coding the search string.

On Wednesday 12 May 2010 10:25:08 Peter Jones wrote:
> We define IBFT_SIGN to "iBFT"; may as well use it.
>

Len,

Were you OK with this patch? I was thinking to send to Linus a git-pull for 
this (and the other patches referenced in this patchset).

> Signed-off-by: Peter Jones <pjones@...hat.com>
> ---
>  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


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/