From: Anatolij Gustschin <agust@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] part_efi: fix build warning
Date: Mon, 31 Oct 2011 16:26:13 +0100 [thread overview]
Message-ID: <20111031162613.509f108c@wker> (raw)
In-Reply-To: <1320073625-7544-1-git-send-email-leiwen@marvell.com>
Hi,
On Mon, 31 Oct 2011 08:07:05 -0700
Lei Wen <leiwen@marvell.com> wrote:
> part_efi.c: In function 'print_part_efi':
> part_efi.c:133: warning: passing argument 3 of 'is_gpt_valid' from
> incompatible pointer type
> part_efi.c:95: note: expected 'struct gpt_header *' but argument is of
> type 'struct gpt_header **'
> part_efi.c: In function 'get_partition_info_efi':
> part_efi.c:172: warning: passing argument 3 of 'is_gpt_valid' from
> incompatible pointer type
> part_efi.c:95: note: expected 'struct gpt_header *' but argument is of
> type 'struct gpt_header **'
>
> Signed-off-by: Lei Wen <leiwen@marvell.com>
> ---
> disk/part_efi.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
A patch for this bug already exists: [1].
Thanks anyway,
Anatolij
[1] http://patchwork.ozlabs.org/patch/122485/
prev parent reply other threads:[~2011-10-31 15:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 15:07 [U-Boot] [PATCH] part_efi: fix build warning Lei Wen
2011-10-31 15:26 ` Anatolij Gustschin [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=20111031162613.509f108c@wker \
--to=agust@denx.de \
--cc=u-boot@lists.denx.de \
/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