All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: hansverk@cisco.com, mchehab+samsung@kernel.org,
	syzbot+be93025dd45dccd8923c@syzkaller.appspotmail.com,
	stable-commits@vger.kernel.org, stable@vger.kernel.org
Subject: Re: Patch "media: vb2: vb2_mmap: move lock up" has been added to the 4.20-stable tree
Date: Mon, 21 Jan 2019 14:52:31 +0100	[thread overview]
Message-ID: <20190121135231.GA29184@kroah.com> (raw)
In-Reply-To: <79a6abad-ba21-b8d0-51b7-039b7e822669@xs4all.nl>

On Mon, Jan 21, 2019 at 02:42:49PM +0100, Hans Verkuil wrote:
> Hi Greg,
> 
> On 01/21/2019 12:51 PM, gregkh@linuxfoundation.org wrote:
> > 
> > This is a note to let you know that I've just added the patch titled
> > 
> >     media: vb2: vb2_mmap: move lock up
> > 
> > to the 4.20-stable tree which can be found at:
> >     http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> > 
> > The filename of the patch is:
> >      media-vb2-vb2_mmap-move-lock-up.patch
> > and it can be found in the queue-4.20 subdirectory.
> > 
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
> 
> This patch must be combined with a backport of c06ef2e9acef4cda1feee2ce055b8086e33d251a
> (media: vb2: be sure to unlock mutex on errors), which fixes a bug introduced by
> this patch.
> 
> It's true for all backports (3.18, 4.9, 4.14, 4.19).

Thanks for letting me know, it's now queued up.

greg k-h

      reply	other threads:[~2019-01-21 14:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <15480714962079@kroah.com>
2019-01-21 13:42 ` Patch "media: vb2: vb2_mmap: move lock up" has been added to the 4.20-stable tree Hans Verkuil
2019-01-21 13:52   ` 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=20190121135231.GA29184@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=hansverk@cisco.com \
    --cc=hverkuil@xs4all.nl \
    --cc=mchehab+samsung@kernel.org \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=syzbot+be93025dd45dccd8923c@syzkaller.appspotmail.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.