From: Ingo Molnar <mingo@elte.hu>
To: Roland McGrath <roland@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: x86 tracehook
Date: Mon, 28 Jul 2008 17:06:34 +0200 [thread overview]
Message-ID: <20080728150634.GC32111@elte.hu> (raw)
In-Reply-To: <20080727063737.09934154280@magilla.localdomain>
* Roland McGrath <roland@redhat.com> wrote:
> Hi! The generic tracehook patches were merged, so now the arch stuff
> can go in any time. These are the pending x86 changes. The only
> difference from what I posted before are fixing up some tiny syntax
> nits in syscall.h that made gcc-3.x unhappy.
>
> Sorry Ingo, I had already done this with git-rebase before I read your
> admonition about that today. (Anyway, the prerequisite tracehook
> series went in via patches rather than a GIT merge, so I don't think
> the x86/tracehook branch forked from my own tracehook branch could
> still have been used.)
that's OK. It only gets painful once someone starts relying on a branch.
> The following changes since commit 8be1a6d6c77ab4532e4476fdb8177030ef48b52c:
> Linus Torvalds (1):
> Merge branch 'for-linus' of git://git.kernel.org/.../roland/infiniband
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/frob/linux-2.6-utrace.git x86-tracehook
>
> Roland McGrath (6):
> x86: tracehook_signal_handler
> x86: tracehook syscall
> x86: tracehook: asm/syscall.h
> x86 signals: use asm/syscall.h
> x86: tracehook: TIF_NOTIFY_RESUME
> x86: tracehook: CONFIG_HAVE_ARCH_TRACEHOOK
pulled into tip/x86/tracehook - thanks Roland!
Ingo
prev parent reply other threads:[~2008-07-28 15:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-27 6:37 Roland McGrath
2008-07-28 15:06 ` Ingo Molnar [this message]
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=20080728150634.GC32111@elte.hu \
--to=mingo@elte.hu \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®