[PATCH 01/13 net-next] net: ipv4: introduce CONFIG_IPV4 to decouple the IPv4 stack
Fernando Fernandez Mancera
fmancera at suse.de
Fri Sep 11 11:39:07 PDT 2026
On 9/10/26 6:56 PM, Sven Eckelmann wrote:
> On Thursday, 10 September 2026 16:48:26 CEST Fernando Fernandez Mancera wrote:
>> diff --git a/net/batman-adv/Kconfig b/net/batman-adv/Kconfig
>> index 58c408b7a7d9..60ad4b09be6e 100644
>> --- a/net/batman-adv/Kconfig
>> +++ b/net/batman-adv/Kconfig
>> @@ -9,6 +9,7 @@
>>
>> config BATMAN_ADV
>> tristate "B.A.T.M.A.N. Advanced Meshing Protocol"
>> + depends on IPV4
>> select CRC32
>> help
>> B.A.T.M.A.N. (better approach to mobile ad-hoc networking) is
>
> This doesn't make a lot of sense to me IPV4 is not a requirement for
> batman-adv. Only very specific features will require symbols from IPv4:
>
> * CONFIG_BATMAN_ADV_BLA
>
> - arp_create
>
> * CONFIG_BATMAN_ADV_DAT
>
> - arp_create
>
> * CONFIG_BATMAN_ADV_MCAST
>
> - ip_mc_check_igmp
>
>
> Basically things which currently depend on INET in net/batman-adv/Kconfig
>
> Or am I missing something here?
>
Yes, you are right. I must re-check all the symbols again. So thank you!
> Regards,
> Sven
More information about the Linux-nvme
mailing list