style: prefix types and functions related to pfcp for consistency #373
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Done to clarify usage, to avoid confusion and to not poison global namespace with conflicting names.
Not all kinds of names renamed, since PR already quite large and it would be easy to miss error.
No changes in logic, only renames. Except
typedef u32 pfcp_timer_t;
was removed, since it was a leftover and proper type waspfcp_timer_ie_t
which is now namedpfcp_ie_timer_t
for consistency.Example renames:
pfcp_node_id_t
=>pfcp_ie_node_id_t
NID_IPv4
=>PFCP_NID_IPv4
format_ur_seqn
=>format_pfcp_ie_ur_seqn
decode_ur_seqn
=>decode_pfcp_ie_ur_seqn
encode_ur_seqn
=>encode_pfcp_ie_ur_seqn
VENDOR_TRAVELPING
=>PFCP_VENDOR_TRAVELPING
pfcp_session_modification_request_t
=>pfcp_msg_session_modification_request_t
- clarificationpfcp_volume_ie_t
=>pfcp_ie_volume_t
- consistencyPFCP_HEARTBEAT_REQUEST
=>PFCP_MSG_HEARTBEAT_REQUEST