Searched hist:"3428785 a65dabf05bc899b6c5334984e98286184" (Results 1 – 9 of 9) sorted by relevance
| /openbmc/linux/fs/dlm/ |
| H A D | util.h | diff 3428785a65dabf05bc899b6c5334984e98286184 Mon Apr 04 15:06:39 CDT 2022 Alexander Aring <aahringo@redhat.com> dlm: use __le types for dlm header
This patch changes to use __le types directly in the dlm header
structure which is casted at the right dlm message buffer positions.
The main goal what is reached here is to remove sparse warnings
regarding to host to little byte order conversion or vice versa. Leaving
those sparse issues ignored and always do it in out/in functionality
tends to leave it unknown in which byte order the variable is being
handled.
Signed-off-by: Alexander Aring <aahringo@redhat.com>
Signed-off-by: David Teigland <teigland@redhat.com>
|
| H A D | util.c | diff 3428785a65dabf05bc899b6c5334984e98286184 Mon Apr 04 15:06:39 CDT 2022 Alexander Aring <aahringo@redhat.com> dlm: use __le types for dlm header
This patch changes to use __le types directly in the dlm header
structure which is casted at the right dlm message buffer positions.
The main goal what is reached here is to remove sparse warnings
regarding to host to little byte order conversion or vice versa. Leaving
those sparse issues ignored and always do it in out/in functionality
tends to leave it unknown in which byte order the variable is being
handled.
Signed-off-by: Alexander Aring <aahringo@redhat.com>
Signed-off-by: David Teigland <teigland@redhat.com>
|
| H A D | requestqueue.c | diff 3428785a65dabf05bc899b6c5334984e98286184 Mon Apr 04 15:06:39 CDT 2022 Alexander Aring <aahringo@redhat.com> dlm: use __le types for dlm header
This patch changes to use __le types directly in the dlm header
structure which is casted at the right dlm message buffer positions.
The main goal what is reached here is to remove sparse warnings
regarding to host to little byte order conversion or vice versa. Leaving
those sparse issues ignored and always do it in out/in functionality
tends to leave it unknown in which byte order the variable is being
handled.
Signed-off-by: Alexander Aring <aahringo@redhat.com>
Signed-off-by: David Teigland <teigland@redhat.com>
|
| H A D | dir.c | diff 3428785a65dabf05bc899b6c5334984e98286184 Mon Apr 04 15:06:39 CDT 2022 Alexander Aring <aahringo@redhat.com> dlm: use __le types for dlm header
This patch changes to use __le types directly in the dlm header
structure which is casted at the right dlm message buffer positions.
The main goal what is reached here is to remove sparse warnings
regarding to host to little byte order conversion or vice versa. Leaving
those sparse issues ignored and always do it in out/in functionality
tends to leave it unknown in which byte order the variable is being
handled.
Signed-off-by: Alexander Aring <aahringo@redhat.com>
Signed-off-by: David Teigland <teigland@redhat.com>
|
| H A D | member.c | diff 3428785a65dabf05bc899b6c5334984e98286184 Mon Apr 04 15:06:39 CDT 2022 Alexander Aring <aahringo@redhat.com> dlm: use __le types for dlm header
This patch changes to use __le types directly in the dlm header
structure which is casted at the right dlm message buffer positions.
The main goal what is reached here is to remove sparse warnings
regarding to host to little byte order conversion or vice versa. Leaving
those sparse issues ignored and always do it in out/in functionality
tends to leave it unknown in which byte order the variable is being
handled.
Signed-off-by: Alexander Aring <aahringo@redhat.com>
Signed-off-by: David Teigland <teigland@redhat.com>
|
| H A D | midcomms.c | diff 3428785a65dabf05bc899b6c5334984e98286184 Mon Apr 04 15:06:39 CDT 2022 Alexander Aring <aahringo@redhat.com> dlm: use __le types for dlm header
This patch changes to use __le types directly in the dlm header
structure which is casted at the right dlm message buffer positions.
The main goal what is reached here is to remove sparse warnings
regarding to host to little byte order conversion or vice versa. Leaving
those sparse issues ignored and always do it in out/in functionality
tends to leave it unknown in which byte order the variable is being
handled.
Signed-off-by: Alexander Aring <aahringo@redhat.com>
Signed-off-by: David Teigland <teigland@redhat.com>
|
| H A D | rcom.c | diff 3428785a65dabf05bc899b6c5334984e98286184 Mon Apr 04 15:06:39 CDT 2022 Alexander Aring <aahringo@redhat.com> dlm: use __le types for dlm header
This patch changes to use __le types directly in the dlm header
structure which is casted at the right dlm message buffer positions.
The main goal what is reached here is to remove sparse warnings
regarding to host to little byte order conversion or vice versa. Leaving
those sparse issues ignored and always do it in out/in functionality
tends to leave it unknown in which byte order the variable is being
handled.
Signed-off-by: Alexander Aring <aahringo@redhat.com>
Signed-off-by: David Teigland <teigland@redhat.com>
|
| H A D | dlm_internal.h | diff 3428785a65dabf05bc899b6c5334984e98286184 Mon Apr 04 15:06:39 CDT 2022 Alexander Aring <aahringo@redhat.com> dlm: use __le types for dlm header
This patch changes to use __le types directly in the dlm header
structure which is casted at the right dlm message buffer positions.
The main goal what is reached here is to remove sparse warnings
regarding to host to little byte order conversion or vice versa. Leaving
those sparse issues ignored and always do it in out/in functionality
tends to leave it unknown in which byte order the variable is being
handled.
Signed-off-by: Alexander Aring <aahringo@redhat.com>
Signed-off-by: David Teigland <teigland@redhat.com>
|
| H A D | lock.c | diff 3428785a65dabf05bc899b6c5334984e98286184 Mon Apr 04 15:06:39 CDT 2022 Alexander Aring <aahringo@redhat.com> dlm: use __le types for dlm header
This patch changes to use __le types directly in the dlm header
structure which is casted at the right dlm message buffer positions.
The main goal what is reached here is to remove sparse warnings
regarding to host to little byte order conversion or vice versa. Leaving
those sparse issues ignored and always do it in out/in functionality
tends to leave it unknown in which byte order the variable is being
handled.
Signed-off-by: Alexander Aring <aahringo@redhat.com>
Signed-off-by: David Teigland <teigland@redhat.com>
|