All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: Jiri Kosina <jikos@kernel.org>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] HID: followup of uhid crashes, and couple of core
Date: Thu, 2 Dec 2021 12:48:52 +0100	[thread overview]
Message-ID: <YaiypPqBRtHDjmMs@kroah.com> (raw)
In-Reply-To: <20211202095334.14399-1-benjamin.tissoires@redhat.com>

On Thu, Dec 02, 2021 at 10:53:30AM +0100, Benjamin Tissoires wrote:
> Hi,
> 
> this is a followup of Greg's series[0].
> hid-sony is having a wrong error path leading to unreleased
> hidraw nodes, and bigbenff is having a crash when used with
> a wrong report descriptor in uhid.
> 
> Those 2 first patches should IMO go into 5.16.
> 
> The 2 others are some core changes I had locally stacked and
> which should be ready to go now. They can be scheduled for 5.16
> or 5.17, there is no rush for them.
> 

Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

  parent reply	other threads:[~2021-12-02 11:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-02  9:53 [PATCH 0/4] HID: followup of uhid crashes, and couple of core Benjamin Tissoires
2021-12-02  9:53 ` [PATCH 1/4] HID: sony: fix error path in probe Benjamin Tissoires
2021-12-02  9:53 ` [PATCH 2/4] HID: bigbenff: prevent null pointer dereference Benjamin Tissoires
2021-12-02  9:53 ` [PATCH 3/4] HID: add suspend/resume helpers Benjamin Tissoires
2021-12-02  9:53 ` [PATCH 4/4] HID: do not inline some hid_hw_ functions Benjamin Tissoires
2021-12-02 11:48 ` Greg Kroah-Hartman [this message]
2021-12-02 16:48   ` [PATCH 0/4] HID: followup of uhid crashes, and couple of core Benjamin Tissoires

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=YaiypPqBRtHDjmMs@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=benjamin.tissoires@redhat.com \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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.