> I'd rather avoid pushing the 2.5.x core code for the dscc4 chipset in
> 2.4 now as some side of it still suck. Is it fine to wait for me to
> update current 2.4.x dscc4 code to new api ? ETA = now + a few days at
> worst.
I can see no problem with that, as long as we are at early 2.4.21 stages.
-- Krzysztof Halasa Network Administrator - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/