public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Thomas Gleixner <tglx@linutronix•de>, Ingo Molnar <mingo@elte•hu>,
	"H. Peter Anvin" <hpa@zytor•com>
Cc: linux-next@vger•kernel.org, Masami Hiramatsu <mhiramat@redhat•com>
Subject: linux-next: tracing tree build failure
Date: Thu, 26 Mar 2009 12:14:59 +1100	[thread overview]
Message-ID: <20090326121459.197d346a.sfr@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 574 bytes --]

Hi all,

Today's linux-next build (x86_64 allmodconfig) failed like this:

arch/x86/kernel/kprobes.c: In function 'trampoline_handler':
arch/x86/kernel/kprobes.c:697: error: 'struct pt_regs' has no member named 'gs'

Caused by commit b9dad0d2955db059cd92c81c37ddcbef0abc8bf8 ("x86:
kretprobe-booster interrupt emulation code fix").  64bit appears to not
have a gs in its pt_regs.

I have used the version of this tree that was in next-20090325 for today.
-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

             reply	other threads:[~2009-03-26  1:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-26  1:14 Stephen Rothwell [this message]
2009-03-26  1:37 ` linux-next: tracing tree build failure Masami Hiramatsu
2009-03-26  7:54   ` Ingo Molnar
2009-03-26  8:04     ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2009-03-10  0:55 Stephen Rothwell
2009-03-10  1:49 ` Tejun Heo
2009-03-10  9:10   ` Ingo Molnar
2009-03-10  2:16 ` KOSAKI Motohiro

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=20090326121459.197d346a.sfr@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=hpa@zytor$(echo .)com \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=mhiramat@redhat$(echo .)com \
    --cc=mingo@elte$(echo .)hu \
    --cc=tglx@linutronix$(echo .)de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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