From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: Stephen Boyd <swboyd@chromium.org>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] HID: ensure timely release of driver-allocated resources
Date: Sat, 6 May 2023 11:38:03 -0700 [thread overview]
Message-ID: <ZFaeiwBp+5hUXk/j@google.com> (raw)
In-Reply-To: <ZFWarGkRAfPOmI6E@google.com>
On Fri, May 05, 2023 at 05:09:16PM -0700, Dmitry Torokhov wrote:
> + if (down_interruptible(&hdev->driver_input_lock))
> + return -EINTR;
> +
> + ret = __hid_device_probe(hdev);
There is an extra space snuck in before "ret", let me know if you want
me to repost it (or if there are bigger concerns).
Thanks.
--
Dmitry
next prev parent reply other threads:[~2023-05-06 18:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-06 0:09 [PATCH] HID: ensure timely release of driver-allocated resources Dmitry Torokhov
2023-05-06 18:38 ` Dmitry Torokhov [this message]
2023-05-22 23:30 ` Dmitry Torokhov
2023-05-23 13:57 ` Jiri Kosina
2023-05-23 21:05 ` Dmitry Torokhov
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=ZFaeiwBp+5hUXk/j@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=benjamin.tissoires@redhat.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=swboyd@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).