From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: linux-next@vger.kernel.org
Subject: Re: Fwd: Re: [PATCH] kprobes: fix compilation break due to kprobe_mutex
Date: Sat, 17 May 2008 22:02:04 +1000 [thread overview]
Message-ID: <20080517220204.d78fdce2.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20080517114244.GB30141@flint.arm.linux.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1066 bytes --]
Hi Russell,
On Sat, 17 May 2008 12:42:45 +0100 Russell King - ARM Linux <linux@arm.linux.org.uk> wrote:
>
> Presumably this hasn't been detected because linux-next isn't building
> enough ARM configurations to hit one that has kprobes enabled?
http://kisskb.ellerman.id.au/kisskb/compiler/11/
That's what I have building for arm. I have asked twice for a suggested
set of configs. Consider this request number three :-)
From: "Abhishek Sagar" <sagar.abhishek@gmail.com>
>
> Now that I look at it, the commit I'm referring to is in
> git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86.git :
> auto-sched-next. I merged all the recent kprobe related changes from
> there into my local arm kprobes branch based on 2.6.26-rc2 and fired a
> build for arm. That's when I encountered the kprobe build error.
Also, that branch isn't in linux-next. The commit maybe but I don't know
what commit is being discussed, sorry.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-05-17 12:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-17 11:42 Fwd: Re: [PATCH] kprobes: fix compilation break due to kprobe_mutex Russell King - ARM Linux
2008-05-17 12:02 ` Stephen Rothwell [this message]
2008-05-17 12:17 ` Stephen Rothwell
2008-05-17 13:35 ` Russell King - ARM Linux
2008-05-17 13:59 ` Stephen Rothwell
2008-05-17 16:20 ` Stephen Rothwell
2008-05-17 19:08 ` Russell King - ARM Linux
2008-05-18 3:49 ` Stephen Rothwell
2008-05-18 3:53 ` Stephen Rothwell
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=20080517220204.d78fdce2.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-next@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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).