> Because loop-AES attempts to be compatible with structures in loop.h by not
> modifying loop.h at all. This is what the "no kernel sources patched or
> replaced" means. Breakage in loop.h breaks loop-AES, and I have to clean the
> mess.
We're in a development stream. It is kind of expected that in-kernel
APIs may change if the developers feel it will lead to some improvement.
This sucks for people that are trying to track those APIs with
out-of-kernel patches, but its a fact of life.
Chris
-- Chris Friesen | MailStop: 043/33/F10 Nortel Networks | work: (613) 765-0557 3500 Carling Avenue | fax: (613) 765-2986 Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com- 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/