Re: Suggestion to turn a nwarn into an ninfo in ipv4_input

2022-06-09 Thread Sebastien Lorquet
Here it is, I hope it does not take two full days for merging :) https://github.com/apache/incubator-nuttx/pull/6399 Sebastien Le 09/06/2022 à 14:30, Sebastien Lorquet a écrit : Hello, I also agree an option is useless. I was just suggesting this in case some people still want to see it as w

Re: Suggestion to turn a nwarn into an ninfo in ipv4_input

2022-06-09 Thread Sebastien Lorquet
Hello, I also agree an option is useless. I was just suggesting this in case some people still want to see it as warning. I'll send a pull request a bit later. Thanks for the feedback! Sebastien Le 09/06/2022 à 14:17, Alan Carvalho de Assis a écrit : I completely agree! We need to reduce

Re: Suggestion to turn a nwarn into an ninfo in ipv4_input

2022-06-09 Thread Alan Carvalho de Assis
I completely agree! We need to reduce the number of configurations, not increase it. Just converting it to ninfo() is enough. Other OS has a good documentation to educate developers to avoid creating unnecessary Kconfig entries: https://doc.riot-os.org/kconfig-in-riot.html https://docs.zephyrpr

Re: Suggestion to turn a nwarn into an ninfo in ipv4_input

2022-06-09 Thread Abdelatif Guettouche
+1 for making it an ninfo (without the extra option). On Thu, Jun 9, 2022 at 8:45 AM Michael Jung wrote: > > Hi Sebastien, > > I have this warning degraded to an informational message in my local > repository for the exact same reason. In my opinion it should just be > changed to informational. I