Re: [I] [HELP] Encapsulating Kconfig options in Arch files [nuttx]

2025-04-15 Thread via GitHub
stbenn commented on issue #16202: URL: https://github.com/apache/nuttx/issues/16202#issuecomment-2807610128 I agree that changing all of the stm32 Kconfigs is probably not worth the effort. The process of splitting them into submenus is relatively easy and quick, but testing the refactor wo

Re: [I] [HELP] Encapsulating Kconfig options in Arch files [nuttx]

2025-04-15 Thread via GitHub
raiden00pl commented on issue #16202: URL: https://github.com/apache/nuttx/issues/16202#issuecomment-2804036165 I'm against this as long as it's a change only for stm32h5. All stm32 ports should look the same for easier maintenance. I don't think multiple Kconfig is a bad idea, I think the

[I] [HELP] Encapsulating Kconfig options in Arch files [nuttx]

2025-04-14 Thread via GitHub
stbenn opened a new issue, #16202: URL: https://github.com/apache/nuttx/issues/16202 ### Description For arch configuration, is it acceptable to use separate Kconfig files for logical blocks of the configuration? I am not proposing rework of already implemented Kconfig files, but wou