From: Matthew Garrett <matthew.garrett-05XSO3Yj/JvQT0dZR+AlfA@public.gmane.org>
To: Joseph Salisbury
<joseph.salisbury-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
Cc: "matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org"
<matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>,
Ingo Molnar <mingo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
"hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org"
<hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>,
"x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org"
<x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
"linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Brad Figg <brad.figg-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
Subject: Re: [RESEND][v3.8] [v3.9] [v3.10] [Regression] efi: be more paranoid about available space when creating variables
Date: Wed, 17 Jul 2013 20:42:02 +0000 [thread overview]
Message-ID: <1374093721.2670.0.camel@x230> (raw)
In-Reply-To: <51E6FFD2.7010505-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
On Wed, 2013-07-17 at 16:34 -0400, Joseph Salisbury wrote:
> Hi Matthew,
>
> A bug was opened that reports a regression that prevents a system from
> booting[0]. After a kernel bisect, it was found that reverting the
> following commit resolved this bug:
This should be fixed by f8b8404337de4e2466e2e1139ea68b1f8295974f
--
Matthew Garrett | mjg59@srcf.ucam.org
prev parent reply other threads:[~2013-07-17 20:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-17 20:34 [RESEND][v3.8] [v3.9] [v3.10] [Regression] efi: be more paranoid about available space when creating variables Joseph Salisbury
[not found] ` <51E6FFD2.7010505-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
2013-07-17 20:42 ` Matthew Garrett [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=1374093721.2670.0.camel@x230 \
--to=matthew.garrett-05xso3yj/jvqt0dzr+alfa@public.gmane.org \
--cc=brad.figg-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org \
--cc=hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org \
--cc=joseph.salisbury-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=mingo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org \
--cc=x86-DgEjT+Ai2ygdnm+yROfE0A@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