public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tom Duffy <tduffy@sun.com>
To: "Langsdorf, Mark" <mark.langsdorf@amd.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	discuss@x86-64.org
Subject: RE: [discuss] [OOPS] powernow on smp dual core amd64
Date: Tue, 14 Jun 2005 11:19:23 -0700	[thread overview]
Message-ID: <1118773163.22484.13.camel@duffman> (raw)
In-Reply-To: <84EA05E2CA77634C82730353CBE3A84301CFC14D@SAUSEXMB1.amd.com>

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

On Mon, 2005-06-13 at 17:44 -0500, Langsdorf, Mark wrote:
> > > Tom, could you try this patch and see if it helps?
> > 
> > Yes!  It fixed the panic.  I get much further.
> 
> Great, I'll test that some more then submit it.

I would like it if this patch could make it into 2.6.12 before it is
released.

Any possibility?

Thanks,

-tduffy

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2005-06-14 18:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-13 22:44 [discuss] [OOPS] powernow on smp dual core amd64 Langsdorf, Mark
2005-06-13 22:47 ` Andi Kleen
2005-06-13 22:58 ` Tom Duffy
2005-06-13 23:35   ` Andi Kleen
2005-06-14 18:19 ` Tom Duffy [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-06-13 21:47 Langsdorf, Mark
2005-06-13 22:20 ` Tom Duffy
2005-06-13 22:38   ` Andi Kleen
2005-06-13 23:17   ` Zachary Amsden
2005-06-13 23:34     ` Andi Kleen
     [not found] <84EA05E2CA77634C82730353CBE3A84301CFC14B@SAUSEXMB1.amd.com>
2005-06-13 21:27 ` Tom Duffy
2005-06-10 19:48 Langsdorf, Mark
2005-06-10 20:01 ` Andi Kleen
2005-06-09 23:46 Tom Duffy
2005-06-10 16:53 ` [discuss] " Andi Kleen
2005-06-10 18:46   ` Tom Duffy

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=1118773163.22484.13.camel@duffman \
    --to=tduffy@sun.com \
    --cc=discuss@x86-64.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.langsdorf@amd.com \
    /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