From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] efi: stub: define DISABLE_BRANCH_PROFILING for all architectures
Date: Wed, 6 Jan 2016 15:43:49 +0000 [thread overview]
Message-ID: <20160106154348.GF16580@arm.com> (raw)
In-Reply-To: <20160105175114.GG10705@arm.com>
On Tue, Jan 05, 2016 at 05:51:14PM +0000, Will Deacon wrote:
> On Tue, Jan 05, 2016 at 03:39:18PM +0000, Matt Fleming wrote:
> > On Tue, 05 Jan, at 03:56:39PM, Ard Biesheuvel wrote:
> > > (+ Arnd)
> > >
> > > On 4 January 2016 at 13:31, Will Deacon <will.deacon@arm.com> 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@arm.com>
> > > >> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.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@arm.com>
> > > >
> > > > 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@codeblueprint.co.uk>
>
> I can take this via the arm64 tree, unless Arnd wants to queue it in
> arm-soc. Arnd?
Given that this fixes build errors, I've applied it in the arm64 tree,
so it should appear in -next soon.
Will
next prev parent reply other threads:[~2016-01-06 15:43 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
2015-12-23 9:33 ` Ard Biesheuvel
2016-01-04 12:31 ` Will Deacon
2016-01-05 14:56 ` Ard Biesheuvel
2016-01-05 15:39 ` Matt Fleming
2016-01-05 17:51 ` Will Deacon
2016-01-06 15:43 ` Will Deacon [this message]
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=20160106154348.GF16580@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).