From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Rob Herring <rob.herring@calxeda.com>,
Grant Likely <grant.likely@secretlab.ca>
Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
Arnd Bergmann <arnd@arndb.de>,
devicetree-discuss@lists.ozlabs.org,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Sylwester Nawrocki <s.nawrocki@samsung.com>
Subject: Compilation breakage on drivers/media due to OF patches - was: Re: [PATCH] DT: export of_get_next_parent() for use by modules: fix modular V4L2
Date: Wed, 17 Apr 2013 11:53:57 -0300 [thread overview]
Message-ID: <20130417115357.0b0f31ae@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1304171555140.16330@axis700.grange>
Hi Grant/Rob,
Our tree is currently _broken_ with OT, because of the lack of
exporting of_get_next_parent. The developer that submitted the patches
that added V4L2 OF support forgot to test to compilation with MODULES
support enabled.
So, we're now having:
ERROR: "of_get_next_parent" [drivers/media/v4l2-core/videodev.ko] undefined!
if compiled with OF enabled and media as module.
As those patches were applied at my master branch and there are lots of
other patches on the top of the patches that added V4L2 OF support,
I prefer to avoid reverting those patches.
On the other hand, I can't send the patches upstream next week (assuming
that -rc7 is the final one), without having this patch applying before
the media tree.
So, please help me solving this issue as soon as possible.
Thank you!
Mauro
Em Wed, 17 Apr 2013 16:07:49 +0200 (CEST)
Guennadi Liakhovetski <g.liakhovetski@gmx.de> escreveu:
> Hi all
>
> On Tue, 2 Apr 2013, Guennadi Liakhovetski wrote:
>
> > On Tue, 2 Apr 2013, Arnd Bergmann wrote:
> >
> > > On Tuesday 02 April 2013, Guennadi Liakhovetski wrote:
> > > > Currently modular V4L2 build with enabled OF is broken dur to the
> > > > of_get_next_parent() function being unavailable to modules. Export it to
> > > > fix the build.
> > > >
> > > > Cc: Sylwester Nawrocki <s.nawrocki@samsung.com>
> > > > Signed-off-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
> > >
> > > Looks good to me, but shouldn't this be EXPORT_SYMBOL_GPL?
> >
> > "grep EXPORT_SYMBOL drivers/of/base.c" doesn't give a certain answer, but
> > it seems to fit other of_get_* functions pretty well:
>
> Ping, could this patch be pushed to -next asap, please? Without it the
> current V4L2 -next doesn't compile. Also, I think, ro avoid breaking the
> mainline, we should try to have this patch pulled in before the media
> tree, could that be done?
>
> Thanks
> Guennadi
>
> > EXPORT_SYMBOL(of_get_parent);
> > +EXPORT_SYMBOL(of_get_next_parent);
> > EXPORT_SYMBOL(of_get_next_child);
> > EXPORT_SYMBOL(of_get_next_available_child);
> > EXPORT_SYMBOL(of_get_child_by_name);
>
> ---
> Guennadi Liakhovetski, Ph.D.
> Freelance Open-Source Software Developer
> http://www.open-technology.de/
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Cheers,
Mauro
next prev parent reply other threads:[~2013-04-17 14:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 16:28 [PATCH] DT: export of_get_next_parent() for use by modules: fix modular V4L2 Guennadi Liakhovetski
2013-04-02 16:30 ` Arnd Bergmann
2013-04-02 16:42 ` Guennadi Liakhovetski
2013-04-17 14:07 ` Guennadi Liakhovetski
2013-04-17 14:53 ` Mauro Carvalho Chehab [this message]
2013-04-17 15:08 ` Compilation breakage on drivers/media due to OF patches - was: " Grant Likely
2013-04-17 15:24 ` 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=20130417115357.0b0f31ae@redhat.com \
--to=mchehab@redhat.com \
--cc=arnd@arndb.de \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=g.liakhovetski@gmx.de \
--cc=grant.likely@secretlab.ca \
--cc=linux-media@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=s.nawrocki@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).