On Mon, Jul 23, 2007 at 11:10:55AM +0200, Guillaume Estival wrote:
> According to Mark, it only requires a minor change on the driver code
> and I will wait for a 4.0r1 to do the job...
The kernel for 4.0r1 is already complete, so there will be no fix
there. This fix will also not appear in 4.0r2 unless we first get
the fix upstream and backport it into the etch kernel.
Mark asked the proper way to proceed. I suggest:
1) submitting the patch upstream and following up until it or an
alternative is accepted.
2) pinging this bug again once that has occurred, at which point we
can consider backporting it
--
dann frazier
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
