Thread (17 messages) 17 messages, 4 authors, 2025-01-09

Re: [PATCH v3 5/6] s390/crash: Use note name macros

From: Dave Martin <Dave.Martin@arm.com>
Date: 2025-01-08 13:50:20
Also in: kexec, linux-mm, linux-s390, lkml

On Wed, Jan 08, 2025 at 01:53:51PM +0900, Akihiko Odaki wrote:
On 2025/01/08 1:17, Dave Martin wrote:
quoted
Hi,

On Tue, Jan 07, 2025 at 09:45:56PM +0900, Akihiko Odaki wrote:
quoted
Use note name macros to match with the userspace's expectation.

Signed-off-by: Akihiko Odaki <redacted>
---
  arch/s390/kernel/crash_dump.c | 62 ++++++++++++++++---------------------------
  1 file changed, 23 insertions(+), 39 deletions(-)
diff --git a/arch/s390/kernel/crash_dump.c b/arch/s390/kernel/crash_dump.c
[...]
quoted
quoted
+#define NT_INIT(buf, type, desc) \
+	(nt_init_name((buf), NT_ ## type, &(desc), sizeof(desc), NN_ ## type))
[...]
quoted
(Note also, the outer parentheses and the parentheses around (buf)
appear redundant -- although harmless?)
They only make a difference in trivial corner cases and may look needlessly
verbose.
(In case there was a misunderstanding here, I meant that some
parentheses can be removed without affecting correctness:

#define NT_INIT(buf, type, desc) \
	nt_init_name(buf, NT_ ## type, &(desc), sizeof(desc), NN_ ## type))

It still doesn't matter though -- and some people do prefer to be
defensive anyway and err on the side of having too many parentheses
rather than too few.)

[...]

Cheers
---Dave
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help