Skip to contentSkip to conversation

EM28xx patches for 3.2

PATCH In review Chris Rankin 2 participants 3 messages Sep 24, 2011 Media (V4L/DVB)

lore
Share & tools
lore
#0 lore raw

cover EM28xx patches for 3.2

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

#1 lore raw

Em 24-09-2011 11:54, Chris Rankin escreveu:

Quoted 4 lines

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.

This one were already applied. Just applied the second one.

Quoted 2 lines

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.

http://git.linuxtv.org/media_tree.git/shortlog/refs/heads/staging/for_v3.2

Quoted 1 line

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().

No, I didn't find any time to look into it. Too much work here...

Regards,
Mauro

Quoted 3 lines

Cheers,
Chris

#2 lore raw

----- Original Message -----

Quoted 4 lines
Quoted 2 lines

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().

No, I didn't find any time to look into it. Too much work here...

OK, then I'd probably better resubmit my final patch as well then.

Cheers,
Chris