Hi, today a sizable portion of the "struct file_operations" variables in the kernel are const, but by far not all. Nor are any of the struct inode_operations const. Marking these read-only datastructures const has the advantage of reducing false sharing of these, often hot, datastructures. In addition there have been cases where drivers or filesystems accidentally and incorrectly wrote to such a struct forgetting that it's a shared datastructure. By marking these const, the compiler will warn/error on such instances.
The series is split up for size, there isn't really any logical order for such a simple search-and-replace operation. Greetings, Arjan van de Ven - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/