Hi, On 4/17/23 11:29, Rahul Rameshbabu wrote: > diff --git a/drivers/hid/Kconfig b/drivers/hid/Kconfig > index 82f64fb31fda..eb19debaa1f5 100644 > --- a/drivers/hid/Kconfig > +++ b/drivers/hid/Kconfig > @@ -990,6 +990,24 @@ config HID_SEMITEK > - Woo-dy > - X-Bows Nature/Knight > > +config HID_SHIELD > + tristate "SHIELD HID Driver" > + depends on USB_HID > + depends on BT_HIDP > + help > + Support for NVIDIA SHIELD accessories. > + > + Supported devices: > + - Thunderstrike (NVIDIA SHIELD Controller 2017) > + > +config SHIELD_FF > + bool "SHIELD force feedback support" > + depends on HID_SHIELD > + select INPUT_FF_MEMLESS > + help > + Say Y here if you would like to enable force feedback support for > + NVIDIA SHIELD accessories with haptics capabilities. According to Documentation/process/coding-style.rst, Kconfig help text should be indented by 2 spaces after the "help" line: 10) Kconfig configuration files ------------------------------- For all of the Kconfig* configuration files throughout the source tree, the indentation is somewhat different. Lines under a ``config`` definition are indented with one tab, while help text is indented an additional two spaces. Example:: config AUDIT bool "Auditing support" depends on NET help Enable auditing infrastructure that can be used with another kernel subsystem, such as SELinux (which requires this for logging of avc messages output). Does not do system-call auditing without CONFIG_AUDITSYSCALL. -- ~Randy
