From: Greg KH <gregkh@linuxfoundation.org>
To: Stefan Ghinea <stefan.ghinea@windriver.com>
Cc: stable@vger.kernel.org,
Pietro Borrello <borrello@diag.uniroma1.it>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>
Subject: Re: [PATCH 6.1 1/2] HID: asus: use spinlock to protect concurrent accesses
Date: Fri, 3 Mar 2023 16:46:55 +0100 [thread overview]
Message-ID: <ZAIWb0R0+wCoxnNd@kroah.com> (raw)
In-Reply-To: <20230301223853.28466-1-stefan.ghinea@windriver.com>
On Thu, Mar 02, 2023 at 12:38:52AM +0200, Stefan Ghinea wrote:
> From: Pietro Borrello <borrello@diag.uniroma1.it>
>
> commit 315c537068a13f0b5681d33dd045a912f4bece6f upstream
>
> asus driver has a worker that may access data concurrently.
> Proct the accesses using a spinlock.
>
> Fixes: af22a610bc38 ("HID: asus: support backlight on USB keyboards")
> Signed-off-by: Pietro Borrello <borrello@diag.uniroma1.it>
> Link: https://lore.kernel.org/r/20230125-hid-unregister-leds-v4-4-7860c5763c38@diag.uniroma1.it
> Signed-off-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
> Signed-off-by: Stefan Ghinea <stefan.ghinea@windriver.com>
> ---
> drivers/hid/hid-asus.c | 22 +++++++++++++++++++++-
> 1 file changed, 21 insertions(+), 1 deletion(-)
What about 6.2.y as well?
Why skip that?
thanks,
greg k-h
prev parent reply other threads:[~2023-03-03 15:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 22:38 [PATCH 6.1 1/2] HID: asus: use spinlock to protect concurrent accesses Stefan Ghinea
2023-03-01 22:38 ` [PATCH 6.1 2/2] HID: asus: use spinlock to safely schedule workers Stefan Ghinea
2023-03-03 15:46 ` Greg KH [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=ZAIWb0R0+wCoxnNd@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=benjamin.tissoires@redhat.com \
--cc=borrello@diag.uniroma1.it \
--cc=stable@vger.kernel.org \
--cc=stefan.ghinea@windriver.com \
/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.