Re: [PATCH] ram: Move Kconfig options into their own menu entry

2025-06-12 Thread Tom Rini
On Mon, 02 Jun 2025 10:15:15 +, Yao Zi wrote: > RAM drivers using Device Model currently lack of their own Kconfig menu > entry, which makes Kconfig put all options of the class in the top-level > menu of device drivers. These options are also incorrectly grouped with > pinctrl options in the

Re: [PATCH] ram: Move Kconfig options into their own menu entry

2025-06-02 Thread Tom Rini
On Mon, Jun 02, 2025 at 10:15:15AM +, Yao Zi wrote: > RAM drivers using Device Model currently lack of their own Kconfig menu > entry, which makes Kconfig put all options of the class in the top-level > menu of device drivers. These options are also incorrectly grouped with > pinctrl options i

Re: [PATCH] ram: Move Kconfig options into their own menu entry

2025-06-02 Thread Quentin Schulz
Hi Yao Zi, On 6/2/25 12:15 PM, Yao Zi wrote: RAM drivers using Device Model currently lack of their own Kconfig menu entry, which makes Kconfig put all options of the class in the top-level menu of device drivers. These options are also incorrectly grouped with pinctrl options in the generated .

[PATCH] ram: Move Kconfig options into their own menu entry

2025-06-02 Thread Yao Zi
RAM drivers using Device Model currently lack of their own Kconfig menu entry, which makes Kconfig put all options of the class in the top-level menu of device drivers. These options are also incorrectly grouped with pinctrl options in the generated .config, which is hard to read. Let's create a me