From: "Rafael Passos" <rafael@rcpassos.me>
To: <sashiko-reviews@lists.linux.dev>, "Rafael Passos" <rafael@rcpassos.me>
Cc: <linux-input@vger.kernel.org>, <dmitry.torokhov@gmail.com>
Subject: Re: [PATCH v5 2/3] HID: wiimote: replace spinlock pairs with scoped_guard
Date: Sun, 11 Oct 2026 09:54:55 -0300 [thread overview]
Message-ID: <DM20WF04H7JK.2HBWS4KGUBW19@rcpassos.me> (raw)
In-Reply-To: <sashiko-outbox-164733@kernel.org>
Oh well, I dont know how this happened.
I will wait for reviews in the rest of the patchset before sending a new version...
On Thu Oct 8, 2026 at 11:44 PM -03, sashiko-bot wrote:
> [Severity: Low]
> This isn't a bug, but could we remove the leading spaces before these #include
> directives? The extra indentation violates the standard kernel coding style.
>
>> + #include <linux/seq_file.h>
>> + #include <linux/spinlock.h>
>> + #include <linux/uaccess.h>
>> + #include "hid-wiimote.h"
next prev parent reply other threads:[~2026-10-11 12:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 2:27 [PATCH v5 0/3] HID: wiimote: new LED behavior on connect + scoped_guards Rafael Passos
2026-10-09 2:27 ` [PATCH v5 1/3] HID: wiimote: turn on the LEDs indicating the controller id Rafael Passos
2026-10-09 2:44 ` sashiko-bot
2026-10-09 2:28 ` [PATCH v5 2/3] HID: wiimote: replace spinlock pairs with scoped_guard Rafael Passos
2026-10-09 2:44 ` sashiko-bot
2026-10-11 12:54 ` Rafael Passos [this message]
2026-10-09 2:28 ` [PATCH v5 3/3] HID: wiimote: led_probe with scoped cleanup Rafael Passos
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=DM20WF04H7JK.2HBWS4KGUBW19@rcpassos.me \
--to=rafael@rcpassos.me \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox