From: Sean Young <sean@mess.org>
To: linux-media@vger.kernel.org
Cc: Heiner Kallweit <hkallweit1@gmail.com>
Subject: [GIT PULL FOR v4.11] RC deadlocks
Date: Wed, 15 Feb 2017 16:06:58 +0000 [thread overview]
Message-ID: <20170215160658.GA6704@gofer.mess.org> (raw)
Hi Mauro,
Two deadlocks which would be nice to have fixed for v4.11. Both were
introduced by the wakeup changes; I guess that teaches me for working
without lockdep enabled.
Thanks,
Sean
The following changes since commit 9eeb0ed0f30938f31a3d9135a88b9502192c18dd:
[media] mtk-vcodec: fix build warnings without DEBUG (2017-02-08 12:08:20 -0200)
are available in the git repository at:
git://linuxtv.org/syoung/media_tree.git for-v4.11d
for you to fetch changes up to 79522eaacc1bc691b419a1c9006da1e494bba5c6:
[media] rc: nuvoton: fix deadlock in nvt_write_wakeup_codes (2017-02-13 13:21:44 +0000)
----------------------------------------------------------------
Heiner Kallweit (1):
[media] rc: nuvoton: fix deadlock in nvt_write_wakeup_codes
Sean Young (1):
[media] lirc: fix dead lock between open and wakeup_filter
drivers/media/rc/lirc_dev.c | 4 ++--
drivers/media/rc/nuvoton-cir.c | 5 +++--
2 files changed, 5 insertions(+), 4 deletions(-)
reply other threads:[~2017-02-15 16:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170215160658.GA6704@gofer.mess.org \
--to=sean@mess.org \
--cc=hkallweit1@gmail.com \
--cc=linux-media@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