Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix #966, update padding in CDS registry struct #969

Closed
wants to merge 2 commits into from

Conversation

jphickey
Copy link
Contributor

Describe the contribution
Makes the 3 bytes of padding here explicit rather than implicit.

Testing performed
Build and sanity check CFE
Issued CFE_ES_DUMP_CDS_REGISTRY_CC command and ensure it is working as expected

Expected behavior changes
None

System(s) tested on
Ubuntu 20.04

Additional Context
Depends on the previous change for #909 ( PR #964 )

Contributor Info - All information REQUIRED for consideration of pull request
Joseph Hickey, Vantage Systems, Inc.

Put all ES typedefs which are shared across API and telemetry
messages into the "cfe_es_extern_typedefs.h" file.

Put all ES typedefs which define the telemetry interface
into the "cfe_es_msg.h" file.  Also include structures which
define the output of commands that write data files into this
group (query all apps, query all tasks, query all CDS).

Removes some localized definitions and replace with MISSION
scope definitions where appropriate/necessary.
As the name field is a multiple of 4 bytes, there needs to be 3 bytes
of padding, not 1, to avoid implicit padding.

This doesn't change anything, it just makes the padding explicit instead
of implicit.
@jphickey jphickey added the CCB:Ready Ready for discussion at the Configuration Control Board (CCB) label Oct 27, 2020
@jphickey
Copy link
Contributor Author

@skliper and @astrogeco on second thought should I just add this commit to #964 instead, since the dependent commit hasn't been merged yet? I can push the commit to the other PR and close this PR - might avoid a merge issue later.

@skliper
Copy link
Contributor

skliper commented Oct 27, 2020

Whichever approach you prefer is fine by me.

@skliper skliper linked an issue Oct 27, 2020 that may be closed by this pull request
@jphickey
Copy link
Contributor Author

Moved to PR #964 because I wanted to fix the name too - having all in a single PR simplifies merging.

@jphickey jphickey closed this Oct 27, 2020
@jphickey jphickey deleted the fix-966-update-padding branch October 27, 2020 16:43
@astrogeco astrogeco added invalid and removed CCB:Ready Ready for discussion at the Configuration Control Board (CCB) labels Oct 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CFE_ES_CDSRegDumpRec_t has implicit padding
3 participants