linux-kernel - Re: linux-next: build failure after merge of the v4l-dvb tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110922201909.GA13347@kroah.com>
Date:	Thu, 22 Sep 2011 13:19:09 -0700
From:	Greg KH <greg@...ah.com>
To:	Mauro Carvalho Chehab <mchehab@...radead.org>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Marek Szyprowski <m.szyprowski@...sung.com>,
	Kyungmin Park <kyungmin.park@...sung.com>
Subject: Re: linux-next: build failure after merge of the v4l-dvb tree

On Thu, Sep 22, 2011 at 09:46:59AM -0300, Mauro Carvalho Chehab wrote:
> Em 22-09-2011 00:12, Stephen Rothwell escreveu:
> > Hi Mauro,
> > 
> > After merging the v4l-dvb tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> > 
> > drivers/staging/dt3155v4l/dt3155v4l.c: In function 'dt3155_start_acq':
> > drivers/staging/dt3155v4l/dt3155v4l.c:210:2: error: implicit declaration of function 'vb2_dma_contig_plane_paddr'
> > drivers/staging/dt3155v4l/dt3155v4l.c: At top level:
> > drivers/staging/dt3155v4l/dt3155v4l.c:321:2: warning: initialization from incompatible pointer type
> > drivers/staging/dt3155v4l/dt3155v4l.c:325:2: warning: initialization from incompatible pointer type
> > 
> > Casued by commit ba7fcb0c9549 ("[media] media: vb2: dma contig allocator:
> > use dma_addr instread of paddr").
> > 
> > I have used the v4l-dvb tree from next-20110921 for today.
> 
> Hi Stephen,
> 
> I think that the right thing to do is to disable the building of this
> staging driver, if it is not using the current media core API's.
> 
> Greg,
> 
> If possible, I prefer to merge those staging drivers for the media
> subsystem via my tree, as it helps me to solve in advance conflicts
> like that. Maybe we could add a drivers/staging/media tree or
> drivers/media/staging, and move those beasts to there.
> 
> What do you think?

Yes, I would _LOVE_ a drivers/staging/media/ directory so that I know
which drivers I am supposed to be ignoring and leaving to you :)

Just let me know which ones I should move into there and I will do that
today and let you maintain them all and just forward any emails to you.
Which will keep issues like this from happening in the future.

thanks,

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