From: Matt Fleming <matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
To: Ard Biesheuvel <ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>,
Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>,
"linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
Catalin Marinas <catalin.marinas-5wv7dgnIgG8@public.gmane.org>
Subject: Re: [PATCH] efi: stub: define DISABLE_BRANCH_PROFILING for all architectures
Date: Tue, 5 Jan 2016 15:39:18 +0000 [thread overview]
Message-ID: <20160105153918.GA2714@codeblueprint.co.uk> (raw)
In-Reply-To: <CAKv+Gu-n-7tk1NXYAbf7+O79gYG82QOsbzLuYG1yX=LSizksWQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Tue, 05 Jan, at 03:56:39PM, Ard Biesheuvel wrote:
> (+ Arnd)
>
> On 4 January 2016 at 13:31, Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org> wrote:
> > On Wed, Dec 23, 2015 at 10:29:28AM +0100, Ard Biesheuvel wrote:
> >> This moves the DISABLE_BRANCH_PROFILING define from the x86 specific
> >> to the general CFLAGS definition for the stub. This fixes build errors
> >> when building for arm64 with CONFIG_PROFILE_ALL_BRANCHES_ENABLED.
> >>
> >> Reported-by: Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>
> >> Signed-off-by: Ard Biesheuvel <ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
> >> ---
> >> drivers/firmware/efi/libstub/Makefile | 4 ++--
> >> 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > Cheers, Ard. The kernel now builds and boots as an EFI application for
> > me when the dreaded #define if config option is enabled:
> >
> > Tested-by: Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>
> >
> > Will
> >
>
> @Matt: this is causing randconfig build errors for ARM in -next. Mind
> if we take this through some other tree?
Go ahead.
Reviewed-by: Matt Fleming <matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
next prev parent reply other threads:[~2016-01-05 15:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-23 9:29 [PATCH] efi: stub: define DISABLE_BRANCH_PROFILING for all architectures Ard Biesheuvel
[not found] ` <1450862968-20222-1-git-send-email-ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-12-23 9:33 ` Ard Biesheuvel
2016-01-04 12:31 ` Will Deacon
[not found] ` <20160104123145.GB1616-5wv7dgnIgG8@public.gmane.org>
2016-01-05 14:56 ` Ard Biesheuvel
[not found] ` <CAKv+Gu-n-7tk1NXYAbf7+O79gYG82QOsbzLuYG1yX=LSizksWQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-01-05 15:39 ` Matt Fleming [this message]
[not found] ` <20160105153918.GA2714-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2016-01-05 17:51 ` Will Deacon
[not found] ` <20160105175114.GG10705-5wv7dgnIgG8@public.gmane.org>
2016-01-06 15:43 ` Will Deacon
[not found] ` <20160106154348.GF16580-5wv7dgnIgG8@public.gmane.org>
2016-01-07 14:59 ` Arnd Bergmann
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=20160105153918.GA2714@codeblueprint.co.uk \
--to=matt-mf/unelci9gs6ibeejttw/xrex20p6io@public.gmane.org \
--cc=ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=catalin.marinas-5wv7dgnIgG8@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=will.deacon-5wv7dgnIgG8@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