From: Rahul Rameshbabu <rrameshbabu@nvidia.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/1] HID: shield: Initial driver implementation with Thunderstrike support
Date: Mon, 17 Apr 2023 12:33:29 -0700 [thread overview]
Message-ID: <87leiqb8xi.fsf@nvidia.com> (raw)
In-Reply-To: <1a754a3e-2a2b-07d5-c94a-0373a1677e4e@infradead.org> (Randy Dunlap's message of "Mon, 17 Apr 2023 12:20:51 -0700")
Hi Randy,
Thanks for the feedback. You are correct about the styling issue in my
patch. I will fix this. I do want to bring to attention that there seem
to be a couple of kernel config options in the Kconfig file for the hid
subsystem that currently violate the styling rules.
It probably would make sense to have a clean-up patch for this issue
overall (separate from this patch, which I will correct in my next
version).
-- Rahul Rameshbabu
On Mon, 17 Apr, 2023 12:20:51 -0700 Randy Dunlap <rdunlap@infradead.org> wrote:
> 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.
prev parent reply other threads:[~2023-04-17 19:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 18:29 [PATCH v3 0/1] HID: shield Rahul Rameshbabu
2023-04-17 18:29 ` [PATCH v3 1/1] HID: shield: Initial driver implementation with Thunderstrike support Rahul Rameshbabu
2023-04-17 19:20 ` Randy Dunlap
2023-04-17 19:33 ` Rahul Rameshbabu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87leiqb8xi.fsf@nvidia.com \
--to=rrameshbabu@nvidia.com \
--cc=benjamin.tissoires@redhat.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.