From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753401AbaIXNTE (ORCPT ); Wed, 24 Sep 2014 09:19:04 -0400 Received: from mail-we0-f174.google.com ([74.125.82.174]:64001 "EHLO mail-we0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752792AbaIXNS7 (ORCPT ); Wed, 24 Sep 2014 09:18:59 -0400 Date: Wed, 24 Sep 2014 15:18:53 +0200 From: Ingo Molnar To: Matt Fleming Cc: Maarten Lankhorst , Ard Biesheuvel , Matt Fleming , Leif Lindholm , Roy Franz , Linus Torvalds , Linux Kernel Mailing List , "H. Peter Anvin" , Thomas Gleixner , Andrew Morton , Josh Boyer Subject: Re: [GIT PULL] x86 fixes Message-ID: <20140924131853.GA12330@gmail.com> References: <20140923055802.GA29052@gmail.com> <1411456851.21380.355.camel@mfleming-mobl1.ger.corp.intel.com> <20140923131805.GH18635@console-pimps.org> <542182E0.6090101@canonical.com> <20140923143712.GI18635@console-pimps.org> <20140924072633.GA1768@gmail.com> <20140924114236.GM18635@console-pimps.org> <20140924130816.GB3277@gmail.com> <20140924131822.GN18635@console-pimps.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140924131822.GN18635@console-pimps.org> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Matt Fleming wrote: > On Wed, 24 Sep, at 03:08:16PM, Ingo Molnar wrote: > > > > * Matt Fleming wrote: > > > > > +/* > > > + * There's no way to return an informative status from this function, > > > + * because any analysis (and printing of error messages) needs to be > > > + * done directly at the EFI function call-site. > > > + * > > > + * For example, EFI_INVALID_PARAMETER could indicate a bug or maybe we > > > + * just didn't find any PCI devices, but there's no way to tell outside > > > + * the context of the call. > > > + */ > > > +static void setup_efi_pci(struct boot_params *params) > > > > Btw., do we print proper complaints at the EFI call sites if such > > failures do happen (and if that failure is unexpected/bad)? > > Not yet, but I've got a patch queued up for v3.18 that does this. Great, thanks! Ingo