linux-efi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matt Fleming <matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
To: Prarit Bhargava <prarit-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Lenny Szubowicz
	<lszubowi-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	Peter Jones <pjones-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Ard Biesheuvel
	<ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Subject: Re: ESRT failures ... was Re: [PATCH 04/11] efi: Add efi_memmap_init_late() for permanent EFI memmap
Date: Tue, 26 Jul 2016 15:26:14 +0100	[thread overview]
Message-ID: <20160726142614.GE31759@codeblueprint.co.uk> (raw)
In-Reply-To: <57974AA4.7090907-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

On Tue, 26 Jul, at 07:33:56AM, Prarit Bhargava wrote:
> 
> I was ping'd by a Dell engineer who says that Dell is taking a look at this.
> Most likely a BIOS fix will be released.
> 
> ... I think that means I should drop the issue :)

It would be valuable if they could still provide details on the issue
though. Not everyone will upgrade their BIOS and it would be nice to
have things work out of the box for those machines currently sat on
shelves in warehouses, i.e. where a fixed BIOS cannot be installed
before the user receives it. 

Feel free to pull whoever pinged you into this thread.

      parent reply	other threads:[~2016-07-26 14:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-13 17:49 ESRT failures ... was Re: [PATCH 04/11] efi: Add efi_memmap_init_late() for permanent EFI memmap Prarit Bhargava
     [not found] ` <57867F32.8040001-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-07-21 12:11   ` Matt Fleming
     [not found]     ` <20160721121136.GF26504-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2016-07-21 14:44       ` Prarit Bhargava
     [not found]         ` <5790DFD0.4020806-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-07-22 13:11           ` Matt Fleming
     [not found]             ` <20160722131101.GJ26504-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2016-07-22 13:31               ` Prarit Bhargava
     [not found]                 ` <57922028.7070103-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-07-25 14:44                   ` Matt Fleming
     [not found]                     ` <20160725144431.GA31759-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2016-07-25 15:11                       ` Prarit Bhargava
     [not found]                         ` <57962C23.5090705-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-07-25 15:13                           ` Matt Fleming
     [not found]                             ` <20160725151344.GB31759-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2016-07-25 15:38                               ` Prarit Bhargava
     [not found]                                 ` <57963289.2090805-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-07-26 11:33                                   ` Prarit Bhargava
     [not found]                                     ` <57974AA4.7090907-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-07-26 14:26                                       ` 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=20160726142614.GE31759@codeblueprint.co.uk \
    --to=matt-mf/unelci9gs6ibeejttw/xrex20p6io@public.gmane.org \
    --cc=ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
    --cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=lszubowi-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=pjones-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=prarit-H+wXaHxf7aLQT0dZR+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;
as well as URLs for NNTP newsgroup(s).