All of lore.kernel.org
 help / color / mirror / Atom feed
From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: fix !CONFIG_COMPAT build failures
Date: Sun, 6 Apr 2014 23:27:39 +0100	[thread overview]
Message-ID: <20140406222737.GA26274@arm.com> (raw)
In-Reply-To: <1396707949-397-1-git-send-email-msalter@redhat.com>

On Sat, Apr 05, 2014 at 03:25:49PM +0100, Mark Salter wrote:
> Recent arm64 builds using CONFIG_ARM64_64K_PAGES are failing with:
> 
>   arch/arm64/kernel/perf_regs.c: In function ?perf_reg_abi?:
>   arch/arm64/kernel/perf_regs.c:41:2: error: implicit declaration of function ?is_compat_thread?
> 
>   arch/arm64/kernel/perf_event.c:1398:2: error: unknown type name ?compat_uptr_t?
> 
> This is due to some recent arm64 perf commits with compat support:
> 
>   commit 23c7d70d55c6d9:
>     ARM64: perf: add support for frame pointer unwinding in compat mode
> 
>   commit 2ee0d7fd36a3f8:
>     ARM64: perf: add support for perf registers API
> 
> Those patches make the arm64 kernel unbuildable if CONFIG_COMPAT is not
> defined and CONFIG_ARM64_64K_PAGES depends on !CONFIG_COMPAT. This patch
> allows the arm64 kernel to build with and without CONFIG_COMPAT.
> 
> Signed-off-by: Mark Salter <msalter@redhat.com>

Thanks. Applied.

-- 
Catalin

WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Mark Salter <msalter@redhat.com>
Cc: Jean Pihet <jean.pihet@linaro.org>,
	Will Deacon <Will.Deacon@arm.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: fix !CONFIG_COMPAT build failures
Date: Sun, 6 Apr 2014 23:27:39 +0100	[thread overview]
Message-ID: <20140406222737.GA26274@arm.com> (raw)
In-Reply-To: <1396707949-397-1-git-send-email-msalter@redhat.com>

On Sat, Apr 05, 2014 at 03:25:49PM +0100, Mark Salter wrote:
> Recent arm64 builds using CONFIG_ARM64_64K_PAGES are failing with:
> 
>   arch/arm64/kernel/perf_regs.c: In function ‘perf_reg_abi’:
>   arch/arm64/kernel/perf_regs.c:41:2: error: implicit declaration of function ‘is_compat_thread’
> 
>   arch/arm64/kernel/perf_event.c:1398:2: error: unknown type name ‘compat_uptr_t’
> 
> This is due to some recent arm64 perf commits with compat support:
> 
>   commit 23c7d70d55c6d9:
>     ARM64: perf: add support for frame pointer unwinding in compat mode
> 
>   commit 2ee0d7fd36a3f8:
>     ARM64: perf: add support for perf registers API
> 
> Those patches make the arm64 kernel unbuildable if CONFIG_COMPAT is not
> defined and CONFIG_ARM64_64K_PAGES depends on !CONFIG_COMPAT. This patch
> allows the arm64 kernel to build with and without CONFIG_COMPAT.
> 
> Signed-off-by: Mark Salter <msalter@redhat.com>

Thanks. Applied.

-- 
Catalin

  reply	other threads:[~2014-04-06 22:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-05 14:25 [PATCH] arm64: fix !CONFIG_COMPAT build failures Mark Salter
2014-04-05 14:25 ` Mark Salter
2014-04-06 22:27 ` Catalin Marinas [this message]
2014-04-06 22:27   ` Catalin Marinas
2014-04-07  8:04   ` Jean Pihet
2014-04-07  8:04     ` Jean Pihet

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=20140406222737.GA26274@arm.com \
    --to=catalin.marinas@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.