From: Matt Fleming <matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: joeyli <jlee-IBi9RG/b67k@public.gmane.org>
Cc: Lingzhu Xiang <lxiang-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Jeremy Kerr <jk-mnsaURCQ41sdnm+yROfE0A@public.gmane.org>,
Matthew Garrett
<matthew.garrett-05XSO3Yj/JvQT0dZR+AlfA@public.gmane.org>,
linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Josh Boyer <jwboyer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Andy Whitcroft <apw-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
Subject: Re: [PATCH] efivarfs: Never return ENOENT from firmware again
Date: Tue, 14 May 2013 08:16:48 +0100 [thread overview]
Message-ID: <5191E4E0.7020505@intel.com> (raw)
In-Reply-To: <1368506197.21417.172.camel-ONCj+Eqt86TasUa73XJKwA@public.gmane.org>
On 05/14/2013 05:36 AM, joeyli wrote:
> I found the "[PATCH] x86, efi: initial the local variable of DataSize to
> zero" lost in urgent branch, and it also didn't in Linus's v3.10-rc1.
>
> Did this patch move to other branch?
It appears I dropped this patch when doing the rebase against -rc1. I'm
really sorry about that. I've applied it again.
Thanks for being so diligent.
next prev parent reply other threads:[~2013-05-14 7:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 10:29 [PATCH] efivarfs: Never return ENOENT from firmware again Lingzhu Xiang
[not found] ` <5b6476bf31dc699a0e6f3983e78447eeac34d831.1368180585.git.lxiang-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-05-13 19:21 ` Matt Fleming
2013-05-14 4:36 ` joeyli
[not found] ` <1368506197.21417.172.camel-ONCj+Eqt86TasUa73XJKwA@public.gmane.org>
2013-05-14 7:16 ` Matt Fleming [this message]
2013-05-14 8:32 ` joeyli
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=5191E4E0.7020505@intel.com \
--to=matt.fleming-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=apw-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org \
--cc=jk-mnsaURCQ41sdnm+yROfE0A@public.gmane.org \
--cc=jlee-IBi9RG/b67k@public.gmane.org \
--cc=jwboyer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lxiang-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=matthew.garrett-05XSO3Yj/JvQT0dZR+AlfA@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