On Tue, Jul 03, 2018 at 02:41:01PM -0400, Mathieu Desnoyers wrote: > User-space won't ever want to read cpu_id_start and cpu_id from a single > u64 load, it serves no purpose to do so. So I'm OK with keeping those as > is and defining a local union for the __put_user() update. So I think previously we had the sequence number and cpuid in there together, and in that case it did want to load them both. But since you made that sequence number dissapear.... -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
