stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Steve Longerbeam <slongerbeam@gmail.com>
Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>, <stable@vger.kernel.org>
Cc: stable@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH v2] media: ov5640: fix use of destroyed mutex
Date: Tue, 17 Mar 2020 22:30:23 +0000	[thread overview]
Message-ID: <20200317223023.BBD7520409@mail.kernel.org> (raw)
In-Reply-To: <20200313131948.13803-1-tomi.valkeinen@ti.com>

Hi

[This is an automated email]

This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all

The bot has tested the following trees: v5.5.9, v5.4.25, v4.19.109, v4.14.173, v4.9.216, v4.4.216.

v5.5.9: Build OK!
v5.4.25: Build OK!
v4.19.109: Build OK!
v4.14.173: Build OK!
v4.9.216: Failed to apply! Possible dependencies:
    19a81c1426c1 ("[media] add Omnivision OV5640 sensor driver")
    34aa88790bad ("[media] ov2640: convert from soc-camera to a standard subdev sensor driver")
    6713c88fd047 ("[media] media: i2c: soc_camera: constify v4l2_subdev_* structures")
    9823f003b96c ("[media] ov2640: fix colorspace handling")
    9cae97221aab ("[media] media: Add a driver for the ov5645 camera sensor")

v4.4.216: Failed to apply! Possible dependencies:
    10d5509c8d50 ("[media] v4l2: remove g/s_crop from video ops")
    163c9bca101c ("[media] tuner.h: rename TUNER_PAD_IF_OUTPUT to TUNER_PAD_OUTPUT")
    19a81c1426c1 ("[media] add Omnivision OV5640 sensor driver")
    21c29de1d090 ("[media] v4l2-subdev.h: Improve documentation")
    32fdc0e1a87c ("[media] uapi/media.h: Fix entity namespace")
    34aa88790bad ("[media] ov2640: convert from soc-camera to a standard subdev sensor driver")
    684ffa2d5538 ("[media] doc-rst: split media_drivers.rst into one file per API type")
    6aad127d37b6 ("[media] v4l2-mc.h: move tuner PAD definitions to this new header")
    8211b187ec64 ("[media] dvbdev: add support for interfaces")
    89cb3ddbe7cc ("[media] doc-rst: Fix conversion for v4l2 core functions")
    8df00a15817e ("[media] media: rename the function that create pad links")
    9823f003b96c ("[media] ov2640: fix colorspace handling")
    9cae97221aab ("[media] media: Add a driver for the ov5645 camera sensor")
    a0cce2a05756 ("[media] dvbdev: create links on devices with multiple frontends")
    d26a5d4350fd ("[media] doc-rst: Convert media API to rst")
    dd3a46bbbe1d ("[media] tvp5150: Add g_mbus_config subdev operation support")
    df2f94e563ed ("[media] dvb: modify core to implement interfaces/entities at MC new gen")


NOTE: The patch will not be queued to stable trees until it is upstream.

How should we proceed with this patch?

-- 
Thanks
Sasha

  reply	other threads:[~2020-03-17 22:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-13  8:22 [PATCH] media: ov5640: fix use of destroyed mutex Tomi Valkeinen
2020-03-13 11:45 ` Laurent Pinchart
2020-03-13 13:19 ` [PATCH v2] " Tomi Valkeinen
2020-03-17 22:30   ` Sasha Levin [this message]
2020-03-19 21:59   ` Benoit Parrot
2020-03-25 12:20   ` [PATCH v3] " Tomi Valkeinen

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=20200317223023.BBD7520409@mail.kernel.org \
    --to=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tomi.valkeinen@ti.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 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).