Skip to content

Use Vendor message types for mctp-bench, mctp-echo#72

Merged
jk-ozlabs merged 3 commits intomainfrom
dev/matt/vendor-msg-type
May 21, 2025
Merged

Use Vendor message types for mctp-bench, mctp-echo#72
jk-ozlabs merged 3 commits intomainfrom
dev/matt/vendor-msg-type

Conversation

@mkj
Copy link
Copy Markdown
Member

@mkj mkj commented Apr 28, 2025

Previously PLDM message type (1) was being used, but it would be better to use a specific type that won't conflict with other uses.

This could still clash with other vendor types, pending future kernel support to distinguish those.

@mkj mkj force-pushed the dev/matt/vendor-msg-type branch from 756a308 to 47042a8 Compare May 15, 2025 04:45
@mkj mkj requested a review from jk-ozlabs May 15, 2025 05:11
Comment thread src/mctp-bench.c Outdated
mkj added a commit to CodeConstruct/usbnvme that referenced this pull request May 15, 2025
Corresponds to change in CodeConstruct/mctp#72

Signed-off-by: Matt Johnston <matt@codeconstruct.com.au>
mkj added 3 commits May 21, 2025 11:33
mctp-bench now uses a distinct message type instead of PLDM.

Signed-off-by: Matt Johnston <matt@codeconstruct.com.au>
mctp-req and mctp-echo now use a distinct message type instead of PLDM.
The length argument is the length of the "payload", with an additional
3 bytes added for message type.

The first buffer byte is no longer printed (it would be incorrect for
len=0 regardless).

Signed-off-by: Matt Johnston <matt@codeconstruct.com.au>
Recent gcc warns when "sizeof" is a first calloc argument.

Signed-off-by: Matt Johnston <matt@codeconstruct.com.au>
@mkj mkj force-pushed the dev/matt/vendor-msg-type branch from 47042a8 to 7a37d50 Compare May 21, 2025 03:34
@jk-ozlabs
Copy link
Copy Markdown
Member

LGTM, thanks!

@jk-ozlabs jk-ozlabs merged commit 7a37d50 into main May 21, 2025
2 checks passed
@jk-ozlabs jk-ozlabs deleted the dev/matt/vendor-msg-type branch May 23, 2025 06:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants