From: Greg KH <gregkh@linuxfoundation.org>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: arnd@arndb.de, arnd@kernel.org, hverkuil-cisco@xs4all.nl,
laurent.pinchart@ideasonboard.com, mchehab+huawei@kernel.org,
stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] media: v4l: ioctl: Fix memory leak in video_usercopy" failed to apply to 4.4-stable tree
Date: Fri, 5 Mar 2021 11:33:55 +0100 [thread overview]
Message-ID: <YEIJE1trsGQzpZ1S@kroah.com> (raw)
In-Reply-To: <20210305101329.GP3@paasikivi.fi.intel.com>
On Fri, Mar 05, 2021 at 12:13:29PM +0200, Sakari Ailus wrote:
> Hi Greg,
>
> On Mon, Mar 01, 2021 at 12:17:20PM +0100, gregkh@linuxfoundation.org wrote:
> >
> > The patch below does not apply to the 4.4-stable tree.
> > If someone wants it applied there, or to any other stable or longterm
> > tree, then please email the backport, including the original git commit
> > id to <stable@vger.kernel.org>.
>
> I've manually backported patches for the stable trees as there have been
> changes in the upstream between the stable trees and the fix. Small changes
> were also needed between different stable kernels.
Thanks for these, all now queued up.
greg k-h
prev parent reply other threads:[~2021-03-05 10:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 11:17 FAILED: patch "[PATCH] media: v4l: ioctl: Fix memory leak in video_usercopy" failed to apply to 4.4-stable tree gregkh
2021-03-05 10:13 ` Sakari Ailus
2021-03-05 10:14 ` [PATCH FOR stable v4.14 1/1] media: v4l: ioctl: Fix memory leak in video_usercopy Sakari Ailus
2021-03-05 10:14 ` [PATCH FOR stable v4.19 " Sakari Ailus
2021-03-05 10:14 ` [PATCH FOR stable v4.4 " Sakari Ailus
2021-03-05 10:14 ` [PATCH FOR stable v4.9 " Sakari Ailus
2021-03-05 10:14 ` [PATCH FOR stable v5.10 " Sakari Ailus
2021-03-05 10:14 ` [PATCH FOR stable v5.4 " Sakari Ailus
2021-03-05 10:33 ` 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=YEIJE1trsGQzpZ1S@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=mchehab+huawei@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox