From: James Simmons <jsimmons@infradead.org>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH] fix Kconfig breakage in drivers/video
Date: Mon, 15 Mar 2010 11:58:58 +0000 [thread overview]
Message-ID: <alpine.LFD.2.00.1003151158031.16108@casper.infradead.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1003151152260.16108@casper.infradead.org>
Hi Krzysztof,
On Sun, Mar 14, 2010 at 10:53:29PM +0100, Krzysztof Helt wrote:
> From: Krzysztof Helt <krzysztof.h1@wp.pl>
>
> There are two new options inside the CONFIG_FB section which do not
> depend on the CONFIG_FB. This break Kconfig menu layout.
>
> Fix it and reduce few conditions for sparc frame buffers
> as the FB_SBUS = ((FB = y) && SPARC).
>
> Signed-off-by: Krzysztof Helt <krzysztof.h1@wp.pl>
> ---
>
> --- linux-orig/drivers/video/Kconfig 2010-03-14 23:54:39.000000000 +0100
> +++ linux-git/drivers/video/Kconfig 2010-03-15 00:05:59.000000000 +0100
> @@ -400,12 +400,9 @@ config FB_SA1100
> If you plan to use the LCD display with your SA-1100 system, say
> Y here.
>
> -config HAVE_FB_IMX
> - bool
> -
> config FB_IMX
> tristate "Motorola i.MX LCD support"
> - depends on FB && (HAVE_FB_IMX || ARCH_MX1 || ARCH_MX2)
> + depends on FB && (ARCH_MX1 || ARCH_MX2)
This hunk reverts f6014419 (imxfb: add support for i.MX25). Is this
intentional?
baruch
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{ - baruch@tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2010-03-15 11:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 11:54 [PATCH] fix Kconfig breakage in drivers/video James Simmons
2010-03-15 11:58 ` James Simmons [this message]
[not found] <20100314225329.f5dc3e05.krzysztof.h1@poczta.fm>
2010-03-14 22:19 ` David Miller
[not found] ` <20100315063919.GB27515@jasper.tkos.co.il>
2010-03-23 19:11 ` Andrew Morton
2010-04-27 22:57 ` Andrew Morton
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=alpine.LFD.2.00.1003151158031.16108@casper.infradead.org \
--to=jsimmons@infradead.org \
--cc=linux-fbdev@vger.kernel.org \
/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).