From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Rob Herring <rob.herring@calxeda.com>,
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: Re: 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 12:24:02 -0300 [thread overview]
Message-ID: <20130417122402.4888e80e@redhat.com> (raw)
In-Reply-To: <20130417150843.5A5A63E2B73@localhost>
Em Wed, 17 Apr 2013 16:08:43 +0100
Grant Likely <grant.likely@secretlab.ca> escreveu:
> On Wed, 17 Apr 2013 11:53:57 -0300, Mauro Carvalho Chehab <mchehab@redhat.com> wrote:
> > 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.
>
> The fix needs to be applied to your tree then. Go ahead and apply it with my ack:
>
> Acked-by: Grant Likely <grant.likely@linaro.org>
Thank you!
> It is no good to apply it to the devicetree -next branch because that
> will still leave your branch broken, even if device tree gets merged
> first.
True.
Thanks,
Mauro
prev parent reply other threads:[~2013-04-17 15:24 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 ` Compilation breakage on drivers/media due to OF patches - was: " Mauro Carvalho Chehab
2013-04-17 15:08 ` Grant Likely
2013-04-17 15:24 ` Mauro Carvalho Chehab [this message]
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=20130417122402.4888e80e@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.