public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: next-0710: CONFIG_PARAVIRT broken on x86_64?
Date: Mon, 14 Jul 2008 10:20:05 -0700	[thread overview]
Message-ID: <487B8AC5.2010503@goop.org> (raw)
In-Reply-To: <s5hod4ywnba.wl%tiwai@suse.de>

Takashi Iwai wrote:
> This seems fixed on linux-next-20080714 magically.
> Thanks for your help, anyway!

Yes, I couldn't reproduce it, but there were some fixes for bugs with 
similar symptoms.

Thanks very much for reporting back,
    J


      reply	other threads:[~2008-07-14 17:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-11  1:33 next-0710: CONFIG_PARAVIRT broken on x86_64? Takashi Iwai
2008-07-10 14:50 ` Jeremy Fitzhardinge
2008-07-11  2:52   ` Takashi Iwai
2008-07-10 19:02     ` Jeremy Fitzhardinge
2008-07-11  7:59       ` Takashi Iwai
2008-07-10 20:12         ` Jeremy Fitzhardinge
2008-07-12  9:15           ` Takashi Iwai
2008-07-16  2:54             ` Takashi Iwai
2008-07-14 17:20               ` Jeremy Fitzhardinge [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=487B8AC5.2010503@goop.org \
    --to=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tiwai@suse.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