From: Helge Hafting <helgehaf@aitel.hist.no>
To: Raphael Manfredi <Raphael_Manfredi@pobox.com>,
linux-kernel@vger.kernel.org
Subject: Re: The buggy APIC of the Abit BP6
Date: Tue, 18 Jun 2002 09:33:33 +0200 [thread overview]
Message-ID: <3D0EE24D.DABA5C69@aitel.hist.no> (raw)
In-Reply-To: aeddc2$jva$1@lyon.ram.loc
Raphael Manfredi wrote:
>
> Quoting Robbert Kouprie <robbert@radium.jvb.tudelft.nl> from ml.linux.kernel:
> :BTW, did you get any explanation why this wasn't applied in -ac or main
> :kernel?
>
> None.
>
> But I know that this patch is dirty because it attacks a hardware-dependent
> layer from a rather generic one. This may be why it's rejected. And it
> may also be completely APIC-BP6 specific.
>
> I also know is that it works for me. ;-)
I'll try it. Have you considered resubmitting the patch,
hidden behind a CONFIG_BROKEN_APIC? That'll keep the code
clean for those with better hardware.
Helge Hafting
next prev parent reply other threads:[~2002-06-18 7:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-14 16:49 The buggy APIC of the Abit BP6 Robbert Kouprie
2002-06-14 18:41 ` Raphael Manfredi
2002-06-18 7:33 ` Helge Hafting [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-18 9:53 Robbert Kouprie
2002-06-12 22:33 Robbert Kouprie
2002-06-13 9:05 ` Helge Hafting
2002-06-13 13:30 ` Robbert Kouprie
2002-06-14 10:54 ` Helge Hafting
2002-06-18 15:30 ` Robbert Kouprie
2002-06-18 15:17 ` Zwane Mwaikambo
2002-06-19 12:47 ` Maciej W. Rozycki
2002-06-19 13:23 ` Robbert Kouprie
2002-06-19 14:03 ` Keith Owens
2002-06-19 14:35 ` Maciej W. Rozycki
2002-06-20 1:50 ` Robbert Kouprie
2002-06-19 14:22 ` Maciej W. Rozycki
2002-06-20 12:21 ` Helge Hafting
2002-06-20 13:10 ` Maciej W. Rozycki
2002-06-21 13:02 ` Helge Hafting
2002-06-20 22:29 ` Kevin Krieser
2002-06-14 15:07 ` Raphael Manfredi
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=3D0EE24D.DABA5C69@aitel.hist.no \
--to=helgehaf@aitel.hist.no \
--cc=Raphael_Manfredi@pobox.com \
--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