From: Matt Fleming <matt-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
To: Ding Tianhong <dingtianhong-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
Cc: Matt Fleming
<matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] firmware: fix the compiller warning
Date: Fri, 20 Jun 2014 10:03:44 +0100 [thread overview]
Message-ID: <20140620090344.GV24049@console-pimps.org> (raw)
In-Reply-To: <53A3B665.3080308-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
On Fri, 20 Jun, at 12:19:49PM, Ding Tianhong wrote:
> When I compile the kernel, found this warning:
>
> In file included from arch/arm64/kernel/efi-stub.c:44:0:
> arch/arm64/kernel/../../../drivers/firmware/efi/fdt.c: In function update_fdt:
> arch/arm64/kernel/../../../drivers/firmware/efi/fdt.c:66:22: warning: unused variable name [-Wunused-variable]
> const char *type, *name;
>
> so remove the unused variable and clean this warning.
>
> Signed-off-by: Ding Tianhong <dingtianhong-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
> ---
> drivers/firmware/efi/fdt.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Thanks, for the report, but I've already queued up a fix from Catalin
and sent a pull request to the tip folks,
http://marc.info/?l=linux-kernel&m=140325482303647
--
Matt Fleming, Intel Open Source Technology Center
WARNING: multiple messages have this Message-ID (diff)
From: Matt Fleming <matt@console-pimps.org>
To: Ding Tianhong <dingtianhong@huawei.com>
Cc: Matt Fleming <matt.fleming@intel.com>,
linux-efi@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] firmware: fix the compiller warning
Date: Fri, 20 Jun 2014 10:03:44 +0100 [thread overview]
Message-ID: <20140620090344.GV24049@console-pimps.org> (raw)
In-Reply-To: <53A3B665.3080308@huawei.com>
On Fri, 20 Jun, at 12:19:49PM, Ding Tianhong wrote:
> When I compile the kernel, found this warning:
>
> In file included from arch/arm64/kernel/efi-stub.c:44:0:
> arch/arm64/kernel/../../../drivers/firmware/efi/fdt.c: In function update_fdt:
> arch/arm64/kernel/../../../drivers/firmware/efi/fdt.c:66:22: warning: unused variable name [-Wunused-variable]
> const char *type, *name;
>
> so remove the unused variable and clean this warning.
>
> Signed-off-by: Ding Tianhong <dingtianhong@huawei.com>
> ---
> drivers/firmware/efi/fdt.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Thanks, for the report, but I've already queued up a fix from Catalin
and sent a pull request to the tip folks,
http://marc.info/?l=linux-kernel&m=140325482303647
--
Matt Fleming, Intel Open Source Technology Center
next prev parent reply other threads:[~2014-06-20 9:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 4:19 [PATCH] firmware: fix the compiller warning Ding Tianhong
2014-06-20 4:19 ` Ding Tianhong
[not found] ` <53A3B665.3080308-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2014-06-20 9:03 ` Matt Fleming [this message]
2014-06-20 9:03 ` Matt Fleming
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=20140620090344.GV24049@console-pimps.org \
--to=matt-hnk1s37rvnbexh+ff434mdi2o/jbrioy@public.gmane.org \
--cc=dingtianhong-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.