From: Matt Fleming <matt-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
To: Daeseok Youn <daeseok.youn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] firmware/efi : use NULL instead of 0 for pointer
Date: Thu, 13 Feb 2014 11:06:25 +0000 [thread overview]
Message-ID: <20140213110625.GD20717@console-pimps.org> (raw)
In-Reply-To: <2817765.zrQqrE3135-yEt5tssq++YB2AIH5/lADM23vB8/Nvlt@public.gmane.org>
On Thu, 13 Feb, at 06:54:48PM, Daeseok Youn wrote:
> From 1c70573009a3b50cef2acaae1e5a8cd350edfe6d Mon Sep 17 00:00:00 2001
> From: Daeseok Youn <daeseok.youn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> Date: Thu, 13 Feb 2014 17:16:36 +0900
> Subject: [PATCH] firmware/efi : use NULL instead of 0 for pointer
>
> following sparse warnings:
>
> drivers/firmware/efi/efivars.c:230:66: warning:
> Using plain integer as NULL pointer
> drivers/firmware/efi/efi.c:236:27: warning:
> Using plain integer as NULL pointer
>
> Signed-off-by: Daeseok Youn <daeseok.youn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> ---
> drivers/firmware/efi/efi.c | 2 +-
> drivers/firmware/efi/efivars.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
This patch doesn't apply because it is corrupt,
fatal: corrupt patch at line 11
Patch failed at 0001 efi: Use NULL instead of 0 for pointer
Please attach the patch in a reply.
--
Matt Fleming, Intel Open Source Technology Center
prev parent reply other threads:[~2014-02-13 11:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 9:54 [PATCH] firmware/efi : use NULL instead of 0 for pointer Daeseok Youn
[not found] ` <2817765.zrQqrE3135-yEt5tssq++YB2AIH5/lADM23vB8/Nvlt@public.gmane.org>
2014-02-13 11:06 ` Matt Fleming [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=20140213110625.GD20717@console-pimps.org \
--to=matt-hnk1s37rvnbexh+ff434mdi2o/jbrioy@public.gmane.org \
--cc=daeseok.youn-Re5JQEeQqe8AvxtiuMwx3w@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 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).