jamal <[EMAIL PROTECTED]> writes: > Lets start with the basics: With this patch, can you still do what you > used to do before the change that broke things for you?
I have put workarounds in place and my drivers are currently working, without any additional patch. So unless something is broken again they of course will continue to work. Does your question means it's ok for you to put nonfunctional things in the kernel, just because they don't apparently break anything? Specifics? - Userspace - kernel signaling: rfc2863_policy and friends. Way too complicated and unreliable. - Strange dev->char access instead of atomic_t. - Unnecesary status duplication - flags and operstate. - minor problems which can be fixed when the major ones are. Care to comment? Yes, this patch is better than, say, the previous one. Kill auto-dormant mode, fix kernel-userspace signaling, kill strange dev->char accesses (flags are enough) and it will make some sense again. -- Krzysztof Halasa - 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
