From: Chris Rankin <rankincj@yahoo.com>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: linux-media@vger.kernel.org
Subject: [PATCH 0/2] EM28xx patches for 3.2
Date: Sat, 24 Sep 2011 15:54:14 +0100 [thread overview]
Message-ID: <4E7DEF16.6070209@yahoo.com> (raw)
Mauro,
I am resending the two patches for the em28xx driver which seem to have been
missed for 3.2. The first one simply removes a stray bit operation on
em28xx_devused, whereas the second tidies up the device/extension list handling.
It is possible that the first patch has been applied already. However, I cannot
be sure because I cannot find a URL anywhere that will show me the current
"HEAD" of the "pending for 3.2" tree.
BTW, did you implement a different solution for the DVB module trying to retake
the dev->lock mutex? Because it looks as if both em28xx_dvb_init() and
em28xx_usb_probe() are still calling mutex_lock().
Cheers,
Chris
next reply other threads:[~2011-09-24 14:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-24 14:54 Chris Rankin [this message]
2011-09-24 15:15 ` [PATCH 0/2] EM28xx patches for 3.2 Mauro Carvalho Chehab
2011-09-24 15:37 ` Chris Rankin
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=4E7DEF16.6070209@yahoo.com \
--to=rankincj@yahoo.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.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