Re: [GIT PULL for 2.6.32] V4L/DVB updates

[Mauro Carvalho Chehab]

Em Sat, 28 Nov 2009 03:57:58 +0100
Hans Verkuil <hverkuil@xxxxxxxxx> escreveu:

> On Friday 27 November 2009 22:40:01 Stefan Lippers-Hollmann wrote:
> > Hi
> > 
> > On Friday 27 November 2009, Mauro Carvalho Chehab wrote:
> > > Hi Linus,
> > > 
> > > Please pull from:
> > >         ssh://master.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-2.6.git for_linus
> > > 
> > > For the following drivers and building fixes:
> > > 
> > >    - radio-gemtek-pci: fix double mutex_lock
> > >    - v4l: add more missing linux/sched.h includes
> > >    - soc-camera: properly initialise the device object when reusing
> > >    - soc-camera: sh_mobile_ceu_camera: call pm_runtime_disable
> > >    - em28xx: fix Reddo DVB-C USB TV Box GPIO
> > >    - davinci: remove stray duplicate config pointer
> > >    - SMS_SIANO_MDTV should depend on HAS_DMA
> > >    - cxusb: Fix hang on DViCO FusionHDTV DVB-T Dual Digital 4 (rev 1)
> > >    - sh_mobile_ceu_camera: fix compile warning
> > >    - Fix wrong parameter order in memset
> > [...]
> > 
> > Please consider cherry picking the following two patches from Hans 
> > Verkuil [1]:
> > - add the missing s2250-loader.h
> > - s2250 mutex patch	
> 
> Good catch. Mauro, can you please add these two as well for 2.6.32? I'm sure
> I marked these two as high-prio patches. This staging driver is actively
> being used and developed so this regression should be fixed.

There were a merge problem when applying those patches at -git. As this is a
staging driver, I opted to just move all patches to linux-next, as there were
no mention on the patch subject mentioned that they are, in fact, fixes.

I'll see what can we do to solve the s2250 compilation breakage.

As Linus didn't merge from this pull request yet, I'll work on a fix, based
on one of the Stefan suggestions, preferably backporting the patches.

-- 

Cheers,
Mauro
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/