AP_DroneCAN: DNAServer: remove preferred allocation support #28100
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.
Nothing is known to support it so it can't be tested. Removing it saves flash and reduces complexity.
I would prefer to add support for it to AP_Periph so it can be tested but tridge said he would prefer to just remove support. Saves 168 bytes of flash on Cube Orange. Would consume 32 bytes to add support to AP_Periph.
Tested on the bench that allocation of new and existing nodes works properly still.