From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
Cc: Javier Martinez Canillas <javier@osg.samsung.com>,
Valdis Kletnieks <Valdis.Kletnieks@vt.edu>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: next-20151222 - compile failure in drivers/media/usb/uvc/uvc_driver.c
Date: Wed, 23 Dec 2015 01:07:31 +0200 [thread overview]
Message-ID: <2247066.MzciOvtu7X@avalon> (raw)
In-Reply-To: <20151222163350.044bd9c4@recife.lan>
Hi Mauro,
On Tuesday 22 December 2015 16:33:50 Mauro Carvalho Chehab wrote:
> Em Tue, 22 Dec 2015 20:06:38 +0200 Laurent Pinchart escreveu:
> > On Tuesday 22 December 2015 09:40:43 Javier Martinez Canillas wrote:
> > > On 12/22/2015 07:18 AM, Valdis Kletnieks wrote:
> > > > next-20151222 fails to build for me:
> > > > CC drivers/media/usb/uvc/uvc_driver.o
> > > >
> > > > drivers/media/usb/uvc/uvc_driver.c: In function 'uvc_probe':
> > > > drivers/media/usb/uvc/uvc_driver.c:1941:32: error: 'struct uvc_device'
> > > > has no member named 'mdev'
> > > >
> > > > if (media_device_register(&dev->mdev) < 0)
> > > > ^
> > > >
> > > > scripts/Makefile.build:258: recipe for target
> > > > 'drivers/media/usb/uvc/uvc_driver.o' failed
> > > >
> > > > 'git blame' points at that line being added in:
> > > >
> > > > commit 1590ad7b52714fddc958189103c95541b49b1dae
> > > > Author: Javier Martinez Canillas <javier@osg.samsung.com>
> > > > Date: Fri Dec 11 20:57:08 2015 -0200
> > > >
> > > > [media] media-device: split media initialization and registration
> > > >
> > > > Not sure what went wrong here.
> > >
> > > It was my forgetting to test with !CONFIG_MEDIA_CONTROLLER...
> > >
> > > Anyways, I've already posted a fix for this:
> > >
> > > https://lkml.org/lkml/2015/12/21/224
> >
> > Thank you for the fix.
> >
> > I know this is an unpopular request, but can't we make this MC rework
> > series bisectable ? We're introducing bugs, which is unavoidable given
> > the scope of the change, and I'm really worried about how difficult we'll
> > make it to debug them if we keep piling even compilation fixes on top.
> >
> > I can spend a day this week rebasing the patches myself if that could
> > help.
>
> Laurent,
>
> The problem is that those patches got merged already at media_tree,
> at the media-controller topic branch.
>
> Any rebase there will break the git copies from all developers that are
> based on it. It will also break the trees at linuxtv.org, since the
> developer trees share objects with media_tree.git, in order to save
> space on the servers.
But that branch hasn't been merged to master, so it doesn't have to be the one
we send upstream, does it ? I'm willing to spend time working on the patches
if it can help.
> What we could try to do is to fold them just before sending the pull
> request upstream, as we're using tags for pull requests.
>
> I'll do that during the merge window, if someone reminds me about
> what patches should be fold. I guess there are only two or three
> patches to be fold, as the only compilation breakages I'm aware are
> the ones related to Javier's patch series that broke media_device
> init from the media devnode creation.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2015-12-22 23:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 10:18 next-20151222 - compile failure in drivers/media/usb/uvc/uvc_driver.c Valdis Kletnieks
2015-12-22 12:40 ` Javier Martinez Canillas
2015-12-22 17:01 ` Valdis.Kletnieks
2015-12-22 18:06 ` Laurent Pinchart
2015-12-22 18:33 ` Mauro Carvalho Chehab
2015-12-22 23:07 ` Laurent Pinchart [this message]
2015-12-23 12:21 ` Mauro Carvalho Chehab
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=2247066.MzciOvtu7X@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=javier@osg.samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@osg.samsung.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;
as well as URLs for NNTP newsgroup(s).