From: Ingo Molnar <mingo@elte.hu>
To: Mike Galbraith <efault@gmx.de>
Cc: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>,
LKML <linux-kernel@vger.kernel.org>,
Jaswinder Singh Rajput <jaswinder@kernel.org>
Subject: Re: x86-tip: xine bustage bisection fingers commit 97286a2b64725aac2d584ddd1f94871f9991d5a1
Date: Tue, 3 Mar 2009 09:03:33 +0100 [thread overview]
Message-ID: <20090303080333.GA11484@elte.hu> (raw)
In-Reply-To: <1236060298.6060.1.camel@marge.simson.net>
* Mike Galbraith <efault@gmx.de> wrote:
> On Mon, 2009-03-02 at 17:20 -0800, Hiroshi Shimamoto wrote:
>
> > I made a patch to fix this issue.
> > This patch is against tip/x86/signal.
>
> Yes, this fixed my xine woes.
Applied, thanks guys!
Ingo
next prev parent reply other threads:[~2009-03-03 8:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-02 9:04 x86-tip: xine bustage bisection fingers commit 97286a2b64725aac2d584ddd1f94871f9991d5a1 Mike Galbraith
2009-03-02 9:33 ` Ingo Molnar
2009-03-02 18:15 ` Hiroshi Shimamoto
2009-03-03 1:20 ` Hiroshi Shimamoto
2009-03-03 6:04 ` Mike Galbraith
2009-03-03 8:03 ` Ingo Molnar [this message]
2009-03-03 8:06 ` [tip:x86/signal] x86, signals: fix xine & firefox bustage Hiroshi Shimamoto
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=20090303080333.GA11484@elte.hu \
--to=mingo@elte.hu \
--cc=efault@gmx.de \
--cc=h-shimamoto@ct.jp.nec.com \
--cc=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox