Jeff Garzik wrote:
On Tue, Jun 05, 2007 at 10:27:19AM -0700, Kok, Auke wrote:
We need to make sure that now that we're getting closer to 2.6.22 we don't
end up killing e100 in it. Should we drop the current fixes in it to be on
the safe side and aim for 2.6.23? I would hate to see an untested codepath
breaking e100 on something like ppc or mips... that will be very painful
I certainly agree with this assessment...
I've been wondering if, based on all this recent work, we should revert
the s-bit stuff and wait for 2.6.23.
I think so. It will be no worse then it was and make the patch that
fixes it clearer.
-Ack
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
