net: posix: fix hostname config conflict with unique updates #97826
+137
−10
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.
Overview
Fixes Kconfig conflict between POSIX networking and unique hostname updates that was introduced in v3.7.1.
Problem
Enabling
CONFIG_POSIX_API=y
auto-selectsCONFIG_POSIX_NETWORKING=y
, which force-selectsCONFIG_NET_HOSTNAME_DYNAMIC=y
. This conflicts withCONFIG_NET_HOSTNAME_UNIQUE_UPDATE=y
, preventing the use of POSIX networking with unique hostname updates.Solution
Decouple
NET_HOSTNAME_MAX_LEN
fromNET_HOSTNAME_DYNAMIC
dependency:NET_HOSTNAME_DYNAMIC
from POSIX networkingTesting
Fixes #95811