From: Shuah Khan <shuahkh@osg.samsung.com>
To: mchehab@kernel.org, hansverk@cisco.com, kgene@kernel.org,
krzk@kernel.org, s.nawrocki@samsung.com,
shailendra.v@samsung.com, shuah@kernel.org, Julia.Lawall@lip6.fr,
kyungmin.park@samsung.com, kamil@wypas.org, jtp.park@samsung.com,
a.hajda@samsung.com
Cc: Shuah Khan <shuahkh@osg.samsung.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] fix lockdep warnings in s5p_mfc and exynos-gsc vb2 drivers
Date: Fri, 13 Oct 2017 17:13:35 -0600 [thread overview]
Message-ID: <cover.1507935819.git.shuahkh@osg.samsung.com> (raw)
Driver mmap functions shouldn't hold lock when calling vb2_mmap(). The
vb2_mmap() function has its own lock that it uses to protect the critical
section.
Reference: commit log for f035eb4e976ef5a059e30bc91cfd310ff030a7d3
Shuah Khan (2):
media: exynos-gsc: fix lockdep warning
media: s5p-mfc: fix lockdep warning
drivers/media/platform/exynos-gsc/gsc-m2m.c | 5 -----
drivers/media/platform/s5p-mfc/s5p_mfc.c | 3 ---
2 files changed, 8 deletions(-)
--
2.7.4
next reply other threads:[~2017-10-13 23:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20171013231531epcas5p2f009317ed58f5177e7a0768b69a62b6c@epcas5p2.samsung.com>
2017-10-13 23:13 ` Shuah Khan [this message]
2017-10-13 23:13 ` [PATCH 1/2] media: exynos-gsc: fix lockdep warning Shuah Khan
2017-10-16 15:18 ` [PATCH v2 " Hans Verkuil
2017-11-07 16:53 ` Shuah Khan
2017-12-08 22:58 ` Shuah Khan
2017-10-13 23:13 ` [PATCH 2/2] media: s5p-mfc: " Shuah Khan
2017-10-16 15:18 ` [PATCH v2 " Hans Verkuil
2017-10-16 12:48 ` [PATCH 0/2] fix lockdep warnings in s5p_mfc and exynos-gsc vb2 drivers Marek Szyprowski
2017-10-16 14:51 ` Shuah Khan
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=cover.1507935819.git.shuahkh@osg.samsung.com \
--to=shuahkh@osg.samsung.com \
--cc=Julia.Lawall@lip6.fr \
--cc=a.hajda@samsung.com \
--cc=hansverk@cisco.com \
--cc=jtp.park@samsung.com \
--cc=kamil@wypas.org \
--cc=kgene@kernel.org \
--cc=krzk@kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=s.nawrocki@samsung.com \
--cc=shailendra.v@samsung.com \
--cc=shuah@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
all inboxes | Powered by JetHome®