LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Prakash Punnoor <prakash@punnoor.de>
Cc: Andi Kleen <andi@firstfloor.org>,
mingo@elte.hu, lenb@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Replace nvidia timer override quirk with pci id list
Date: Sat, 9 Feb 2008 12:06:37 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.1.00.0802091140170.3145@apollo.tec.linutronix.de> (raw)
In-Reply-To: <200802090008.05430.prakash@punnoor.de>
On Sat, 9 Feb 2008, Prakash Punnoor wrote:
> On the day of Friday 08 February 2008 Andi Kleen hast written:
> > On Fri, Feb 08, 2008 at 08:00:39PM +0100, Prakash Punnoor wrote:
> > > On the day of Friday 08 February 2008 Andi Kleen hast written:
> > > > On Fri, Feb 08, 2008 at 06:39:17PM +0100, Prakash Punnoor wrote:
> > > > >
> > > > > Yes, confirmed. timer w/o the skipping stays XT-PIC on nforce2.
> > > >
> > > > Confirmed what? Did you test my patch on both machines?
> > > > What was the result?
> > >
> > > I confirmed that it (nforce2) needed the acpi_skip_timer_override. If you
> > > read my mail, you knew I didn't test your patch.
> >
> > Ok can you please do so then? Or stop your obstructism?
>
> Grr, I don't know why I am discussing with stubborn and/or arrogant devs like
> you seem to be. But I actually did what you wanted and as *expected* - as I
> said I understand that trivial piece of code you posted - your patch fails
> here for my nforce2:
No worry, this patch wont go anywhere near mainline as long as it
breaks stuff and obviously you are under no obligation to re-test
patches that have not been changed just re-submitted.
x86 changes, which are considered for mainline are staged in the mm
branch of the x86 git tree:
http://git.kernel.org/?p=linux/kernel/git/x86/linux-2.6-x86.git;a=shortlog;h=mm
Instructions for checking it out are here:
http://people.redhat.com/mingo/x86.git/README
Please let us know, if there is anything which breaks your box(en).
Thanks for your feedback and patience.
tglx
next prev parent reply other threads:[~2008-02-09 11:07 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 19:55 Andi Kleen
2008-02-07 21:21 ` Prakash Punnoor
2008-02-08 11:36 ` Andi Kleen
2008-02-08 15:13 ` Prakash Punnoor
2008-02-08 15:18 ` Prakash Punnoor
2008-02-08 16:09 ` Andi Kleen
2008-02-08 17:39 ` Prakash Punnoor
2008-02-08 19:01 ` Andi Kleen
2008-02-08 19:00 ` Prakash Punnoor
2008-02-08 21:02 ` Andi Kleen
2008-02-08 23:08 ` Prakash Punnoor
2008-02-09 11:06 ` Thomas Gleixner [this message]
2008-02-09 12:18 ` Prakash Punnoor
2008-02-09 11:59 ` Andi Kleen
2008-02-09 11:53 ` Prakash Punnoor
2008-02-09 14:31 ` Andi Kleen
2008-02-09 15:51 ` Prakash Punnoor
2008-02-09 16:56 ` Andi Kleen
2008-02-09 17:30 ` Prakash Punnoor
2008-02-09 12:17 ` [PATCH] Replace nvidia timer override quirk with pci id list II Andi Kleen
2010-01-29 8:32 ` [PATCH] Replace nvidia timer override quirk with pci id list Yuhong Bao
2008-02-09 12:46 ` Gene Heskett
2008-02-09 14:18 ` Andi Kleen
2008-02-09 14:03 ` Alan Cox
2008-02-09 18:02 ` Gene Heskett
2008-02-09 18:11 ` Prakash Punnoor
2008-02-09 20:05 ` Gene Heskett
2008-02-09 21:13 ` Prakash Punnoor
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=alpine.LFD.1.00.0802091140170.3145@apollo.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=andi@firstfloor.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=prakash@punnoor.de \
--subject='Re: [PATCH] Replace nvidia timer override quirk with pci id list' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).