All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
	Tobias Diedrich <ranma+kernel@tdiedrich.de>,
	Yinghai Lu <yinghai.lu@amd.com>, Andrew Morton <akpm@osdl.org>,
	Andi Kleen <ak@suse.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	mingo@redhat.com, discuss@x86-64.org
Subject: Re: [PATCH 4/4] x86_64 ioapic: Improve the heuristics for when check_timer fails.
Date: Mon, 8 Jan 2007 21:21:05 +0100	[thread overview]
Message-ID: <20070108202105.GB6167@stusta.de> (raw)
In-Reply-To: <m18xgdijmb.fsf_-_@ebiederm.dsl.xmission.com>

On Mon, Jan 08, 2007 at 09:11:24AM -0700, Eric W. Biederman wrote:
> 
> To a large extent this reverts b026872601976f666bae77b609dc490d1834bf77
> while still keeping to the spirits of it's goal, the ability to
> make smart guesses about how the timer irq is routed when the BIOS
> gets it wrong.
>...

That's code where every changed line has a great potential of causing a 
different kind of breakage on someone else's computer.

Your comment therefore translates to "revert commit 
b026872601976f666bae77b609dc490d1834bf77 for 2.6.20 and try to find a 
better solution for 2.6.21".

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2007-01-08 22:21 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5986589C150B2F49A46483AC44C7BCA490733F@ssvlexmb2.amd.com>
2007-01-03  6:23 ` 2.6.20-rc3: known unfixed regressions - x86_64 boot failure: "IO-APIC + timer doesn't work" Yinghai Lu
2007-01-08  0:55   ` Tobias Diedrich
2007-01-08  1:09     ` Linus Torvalds
2007-01-08 15:49       ` [PATCH 1/4] x86_64 io_apic: Implement remove_pin_to_irq Eric W. Biederman
2007-01-08 15:53         ` PATCH 2/4] x86_64 io_apic: Implement irq_from_pin Eric W. Biederman
2007-01-08 15:56           ` [PATCH 3/4] x86_64 io_apic: Implment update_irq0_entry Eric W. Biederman
2007-01-08 16:11             ` [PATCH 4/4] x86_64 ioapic: Improve the heuristics for when check_timer fails Eric W. Biederman
2007-01-08 20:21               ` Adrian Bunk [this message]
2007-01-08 21:45                 ` Eric W. Biederman
2007-01-08 22:33                   ` Adrian Bunk
2007-01-08 22:57                     ` Linus Torvalds
2007-01-08 23:14                     ` [discuss] " Andi Kleen
2007-01-08 23:21                       ` Adrian Bunk
2007-01-08 23:18                     ` Eric W. Biederman
2007-01-09 22:00               ` Tobias Diedrich
2007-01-08 17:16 Lu, Yinghai
2007-01-08 20:46 ` Eric W. Biederman
  -- strict thread matches above, loose matches on Subject: below --
2007-01-08 17:41 Lu, Yinghai
2007-01-08 20:39 ` Eric W. Biederman
2007-01-08 20:53 Lu, Yinghai
2007-01-08 21:33 ` Eric W. Biederman
2007-01-09 22:15 Lu, Yinghai
2007-01-10 10:30 ` Tobias Diedrich

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=20070108202105.GB6167@stusta.de \
    --to=bunk@stusta.de \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=discuss@x86-64.org \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=ranma+kernel@tdiedrich.de \
    --cc=torvalds@osdl.org \
    --cc=yinghai.lu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.