public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Matt Fleming <matt@console-pimps.org>
Cc: Valentin Rothberg <valentinrothberg@gmail.com>,
	Ingo Molnar <mingo@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
	Leif Lindholm <leif.lindholm@linaro.org>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: [GIT PULL] EFI urgent fixes
Date: Fri, 26 Sep 2014 13:59:15 +0200	[thread overview]
Message-ID: <1411732755.7866.24.camel@x220> (raw)
In-Reply-To: <20140926114454.GV18635@console-pimps.org>

On Fri, 2014-09-26 at 12:44 +0100, Matt Fleming wrote:
> On Fri, 26 Sep, at 01:27:34PM, Paul Bolle wrote:
> > 
> > This Makefile was changed in the first patch. That became 84be880560fb
> > ("Revert "efi/x86: efistub: Move shared dependencies to <asm/efi.h>""),
> > which just landed in next-20140926.
> > 
> > It appears to have introduced a typo, because:
> >     CONFIG_EFI_ARM_STUB
> > 
> > should probably have been:
> >     CONFIG_EFI_ARMSTUB
> 
> Crap. Thanks for catching that Paul. I'm wondering how this slipped
> through because that commit has an explicit Tested-by from Leif.
> 
> Hell, even I built an arm64 EFI kernel before sending that commit.
> 
> Ohh.. I see why no one caught this. From arch/arm64/Makefile,
> 
>   libs-$(CONFIG_EFI_STUB) += drivers/firmware/efi/libstub/
> 
> so libstub will be built for arm64 regardless of the broken logic in
> drivers/firmware/efi/Makefile.
> 
> Paul, how did you notice the typo? Did you hit an explicit build
> failure? It's definitely wrong and I'm trying to figure out whether I
> need to add some more testing to my build infrastructure to catch this
> kind of problem in the future.

I have a 800 line perl monster that checks for stuff like this. It's not
very sophisticated but smart enough to spot typos like this one. I try
to have it check each linux-next (and mainline) release.

(I think Valentin Rothberg is trying to automate this properly. See
http://www.linuxplumbersconf.org/2014/ocw/sessions/1863 .)

> The next question is: should we fix this up at this point in the merge
> cycle? It's basically just dead code.


Paul Bolle


  reply	other threads:[~2014-09-26 11:59 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-25  7:31 [GIT PULL] EFI urgent fixes Matt Fleming
2014-09-25 14:41 ` Ingo Molnar
2014-09-25 14:44   ` Matt Fleming
2014-09-26 11:27   ` Paul Bolle
2014-09-26 11:35     ` Ingo Molnar
2014-09-26 12:24       ` Matt Fleming
2014-09-27  5:49         ` Ingo Molnar
2014-09-26 11:44     ` Matt Fleming
2014-09-26 11:59       ` Paul Bolle [this message]
2014-09-26 12:34         ` Matt Fleming
2014-09-26 12:55           ` Paul Bolle
2014-09-27  8:04           ` Valentin Rothberg
2014-09-27  9:59             ` Paul Bolle
  -- strict thread matches above, loose matches on Subject: below --
2015-07-30 21:06 Matt Fleming
2015-07-31  7:56 ` Ingo Molnar
2015-05-05 16:27 Matt Fleming
2015-05-06  6:31 ` Ingo Molnar
2015-03-02 12:51 Matt Fleming
2015-03-02 13:24 ` Ingo Molnar
2015-03-02 13:35   ` Matt Fleming
2015-02-18 11:55 Matt Fleming
2015-02-18 13:43 ` Ingo Molnar
2015-02-18 16:36   ` Ard Biesheuvel
2015-02-18 16:57     ` Ingo Molnar
2014-09-08 21:55 Matt Fleming
2014-09-09  5:07 ` Ingo Molnar
2014-09-09  7:07   ` Matt Fleming
2014-09-09 14:55     ` Ingo Molnar
2014-08-22  7:52 Matt Fleming
2014-08-22  8:15 ` Ingo Molnar
2014-07-14 12:54 Matt Fleming
2014-06-27 14:51 Matt Fleming
2014-06-04 16:53 Matt Fleming
2014-04-11  7:16 Matt Fleming
2014-04-11  8:27 ` Ingo Molnar
2014-02-14 13:08 Matt Fleming
2013-11-29 12:09 Matt Fleming
2013-07-11 11:16 Matt Fleming
2013-06-07 11:50 Matt Fleming
2013-06-10 21:36 ` Matt Fleming
2013-05-17 10:18 Matt Fleming
2013-04-25  8:49 Matt Fleming

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=1411732755.7866.24.camel@x220 \
    --to=pebolle@tiscali.nl \
    --cc=ard.biesheuvel@linaro.org \
    --cc=hpa@zytor.com \
    --cc=leif.lindholm@linaro.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt@console-pimps.org \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=valentinrothberg@gmail.com \
    /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