From: tixy@yxit.co.uk (Tixy)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 3/5] ARM: kprobes: Reference cpu_architecture as a global variable
Date: Wed, 10 Aug 2011 12:43:56 +0100 [thread overview]
Message-ID: <1312976636.7800.32.camel@computer2> (raw)
In-Reply-To: <1312971223-28165-4-git-send-email-dave.martin@linaro.org>
On Wed, 2011-08-10 at 11:13 +0100, Dave Martin wrote:
> This patch is needed for compatibility with the change of
> cpu_architecture from a function to a global variable.
>
> Since cpu_architecture is ARM-specific, also add an explicit
> include for <asm/system.h> rather than relying on this being
> included as a side-effect.
>
> Signed-off-by: Dave Martin <dave.martin@linaro.org>
> ---
> arch/arm/kernel/kprobes-common.c | 11 +++++------
> 1 files changed, 5 insertions(+), 6 deletions(-)
Is there any reason that this patch isn't part of the other ARM platform
changes in patch one?
--
Tixy
next prev parent reply other threads:[~2011-08-10 11:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 10:13 [RFC PATCH 0/5] Fix Thumb-2 undef handling for mixed-arch kernels Dave Martin
2011-08-10 10:13 ` [RFC PATCH 1/5] ARM: Make cpu_alignment into a global variable Dave Martin
2011-08-10 11:38 ` Tixy
2011-08-10 10:13 ` [RFC PATCH 2/5] ARM: s3c24xx: Reference cpu_architecture as " Dave Martin
2011-08-10 10:13 ` [RFC PATCH 3/5] ARM: kprobes: " Dave Martin
2011-08-10 11:43 ` Tixy [this message]
2011-08-10 10:13 ` [RFC PATCH 4/5] ARM: entry: Remove unnecessary masking when decoding Thumb-2 instructions Dave Martin
2011-08-10 10:13 ` [RFC PATCH 5/5] ARM: entry: Fix Thumb-2 undef handling for multi-CPU kernels Dave Martin
2011-08-10 11:55 ` Tixy
2011-08-11 13:04 ` Dave Martin
2011-09-01 14:52 ` Arnd Bergmann
2011-09-07 10:54 ` Dave Martin
2011-09-12 10:33 ` Dave Martin
2011-08-10 11:31 ` [RFC PATCH 0/5] Fix Thumb-2 undef handling for mixed-arch kernels Tixy
2011-08-11 13:10 ` Dave Martin
2011-08-15 23:13 ` Nicolas Pitre
2011-08-16 9:04 ` Dave Martin
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=1312976636.7800.32.camel@computer2 \
--to=tixy@yxit.co.uk \
--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.