Alan Cox wrote: >> Thus 'set' has always been an illusion for libata. It's really been >> read-only. > > Which nicely solves the flags2 problem - we have flags, and we have > dynamic flags and if we move the other changing flags into dynflags over > time all will be happy. Umm... there's already ap->pflags for the purpose and it was splitted out for exactly the same reason. If we're running out of flags space, I think we better switch to bitfields than introducing flagsN and risking testing/setting the wrong flag to the wrong field. Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
