gpu: nvgpu: field position in gpu characteristics

Fields added to nvgpu_gpu_characteristics must be before the
/* Notes: .. */ section. Otherwise, there is a possibility that
cherry-picks for new fields actually go before "Notes" and that
breaks binary compatibility.

Jira DNVGPU-186

Change-Id: Idcd5100be357c187e7194d4c9577f85e12541053
Signed-off-by: Thomas Fleury <tfleury@nvidia.com>
Reviewed-on: http://git-master/r/1284324
Reviewed-by: Sami Kiminki <skiminki@nvidia.com>
GVS: Gerrit_Virtual_Submit
Reviewed-by: Terje Bergstrom <tbergstrom@nvidia.com>
This commit is contained in:
Thomas Fleury
2017-01-12 09:14:51 -08:00
committed by mobile promotions
parent f6a634ff24
commit 5d7253ea02

View File

@@ -225,6 +225,9 @@ struct nvgpu_gpu_characteristics {
__u32 reg_ops_limit;
__u32 reserved1;
__s16 event_ioctl_nr_last;
__u16 pad[3];
/* Notes:
- This struct can be safely appended with new fields. However, always
keep the structure size multiple of 8 and make sure that the binary
@@ -232,8 +235,6 @@ struct nvgpu_gpu_characteristics {
- If the last field is reserved/padding, it is not
generally safe to repurpose the field in future revisions.
*/
__s16 event_ioctl_nr_last;
__u16 pad[3];
};
struct nvgpu_gpu_get_characteristics {