On Mon, Aug 27, 2018 at 08:30:23PM +0100, Tim Small wrote:
> On that basis, I don't see a problem with removing it, but if there's a
> preference for me to fix it, (and if I still have some old hardware
> somewhere that I can test it on), I'll be happy to do that instead.
Well, if you don't have
On Mon, Aug 27, 2018 at 08:30:23PM +0100, Tim Small wrote:
> On that basis, I don't see a problem with removing it, but if there's a
> preference for me to fix it, (and if I still have some old hardware
> somewhere that I can test it on), I'll be happy to do that instead.
Well, if you don't have
On 27/08/18 17:45, Borislav Petkov wrote:
> Actually, looking at this driver more - it has been depending on
> BROKEN since 2007!
Hi,
I'd forgotten that it was in BROKEN state.
The issue was that the driver was fully functioning, but it clashed with
the graphics aperture driver - both use
On 27/08/18 17:45, Borislav Petkov wrote:
> Actually, looking at this driver more - it has been depending on
> BROKEN since 2007!
Hi,
I'd forgotten that it was in BROKEN state.
The issue was that the driver was fully functioning, but it clashed with
the graphics aperture driver - both use
nd no one has made the move to fix it. Well, here's a "fix" - let's see if
anyone moves now...
---
From: Borislav Petkov
Date: Mon, 27 Aug 2018 18:39:28 +0200
Subject: [PATCH] EDAC: Remove the i82443bxgx_edac driver
It has been marked BROKEN since 2007:
28f96eeafc89 ("drivers/e
nd no one has made the move to fix it. Well, here's a "fix" - let's see if
anyone moves now...
---
From: Borislav Petkov
Date: Mon, 27 Aug 2018 18:39:28 +0200
Subject: [PATCH] EDAC: Remove the i82443bxgx_edac driver
It has been marked BROKEN since 2007:
28f96eeafc89 ("drivers/e
6 matches
Mail list logo
