From: Lucas Stach <l.stach@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 1/2] video: vpl: depend on OFTREE
Date: Wed, 19 Aug 2015 15:48:18 +0200 [thread overview]
Message-ID: <1439992098.31432.16.camel@pengutronix.de> (raw)
In-Reply-To: <20150819134634.GT18700@pengutronix.de>
Am Mittwoch, den 19.08.2015, 15:46 +0200 schrieb Sascha Hauer:
> On Tue, Aug 18, 2015 at 10:18:24AM +0200, Lucas Stach wrote:
> > VPL uses the of_graph bindings, which are only available if OFTREE
> > support is compiled in.
> >
> > Also fix the drivers using VPL to depend on OFTREE.
> >
> > Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
> > ---
> > drivers/video/Kconfig | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> > diff --git a/drivers/video/Kconfig b/drivers/video/Kconfig
> > index bb8bbb539481..5ecac4209696 100644
> > --- a/drivers/video/Kconfig
> > +++ b/drivers/video/Kconfig
> > @@ -13,6 +13,7 @@ config FRAMEBUFFER_CONSOLE
> > prompt "framebuffer console support"
> >
> > config VIDEO_VPL
> > + depends on OFTREE
> > bool
> >
> > config DRIVER_VIDEO_ATMEL
> > @@ -122,6 +123,7 @@ config DRIVER_VIDEO_MTL017
> > select VIDEO_VPL
> > depends on I2C
> > depends on GPIOLIB
> > + depends on OFTREE
>
> This doesn't apply neither on master nor on next. Where shall this patch
> be applied?
>
On top of the previous randcfg fixes series I sent out earlier.
Regards,
Lucas
--
Pengutronix e.K. | Lucas Stach |
Industrial Linux Solutions | http://www.pengutronix.de/ |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2015-08-19 13:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 8:18 Lucas Stach
2015-08-18 8:18 ` [PATCH 2/2] video: imx-hdmi: depend on EDID support Lucas Stach
2015-08-19 13:46 ` [PATCH 1/2] video: vpl: depend on OFTREE Sascha Hauer
2015-08-19 13:48 ` Lucas Stach [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=1439992098.31432.16.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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