From: Dave Jones <davej@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>,
linux-omap <linux-omap@vger.kernel.org>,
linux-fbdev <linux-fbdev@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
Subject: Re: [GIT PULL] fbdev changes for 3.8
Date: Sat, 15 Dec 2012 17:24:32 -0500 [thread overview]
Message-ID: <20121215222431.GA7153@redhat.com> (raw)
In-Reply-To: <CA+55aFz9+3mOZcjJ9C-izKkidT9mxeO7xUubJER0OTjcZjE=2A@mail.gmail.com>
On Sat, Dec 15, 2012 at 01:11:04PM -0800, Linus Torvalds wrote:
> On Fri, Dec 14, 2012 at 2:22 AM, Tomi Valkeinen <tomi.valkeinen@ti.com> wrote:
> > Hi Linus,
> >
> > Florian, the fbdev maintainer, has been very busy lately, so I offered to send
> > the pull request for fbdev for this merge window.
>
> Pulled. However, with this I get the Kconfig question
>
> OMAP2+ Display Subsystem support (OMAP2_DSS) [N/m/y/?] (NEW)
>
> which doesn't make a whole lot of sense on x86-64, unless there's
> something about OMAP2 that I don't know.
>
> So I'd suggest making that OMAP2_DSS be dependent on OMAP2. Or at
> least ARM. Because showing it to anybody else seems insane.
>
> Same goes for FB_OMAP2 for that matter. I realize that it's likely
> nice to get compile testing for this on x86-64 too, but if that's the
> intent, we need to think about it some more. I don't think it's good
> to ask actual normal users questions like this just for compile
> coverage.
This OMAP stuff has been creeping into x86 builds for a while.
Grep from my current build config ..
# CONFIG_OMAP_OCP2SCP is not set
# CONFIG_KEYBOARD_OMAP4 is not set
# CONFIG_OMAP2_DSS is not set
# CONFIG_OMAP_USB2 is not set
There was some other arm-ism that does the same that I' currently forgetting,
or maybe that got fixed..
Dave
next prev parent reply other threads:[~2012-12-15 22:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 10:22 [GIT PULL] fbdev changes for 3.8 Tomi Valkeinen
2012-12-15 21:11 ` Linus Torvalds
2012-12-15 22:24 ` Dave Jones [this message]
2012-12-16 17:46 ` Tony Lindgren
2012-12-16 20:35 ` Tony Lindgren
2012-12-17 6:00 ` Dmitry Torokhov
2012-12-17 18:29 ` Tony Lindgren
2012-12-17 9:03 ` Tomi Valkeinen
2012-12-17 10:05 ` Felipe Balbi
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=20121215222431.GA7153@redhat.com \
--to=davej@redhat.com \
--cc=FlorianSchandinat@gmx.de \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tomi.valkeinen@ti.com \
--cc=torvalds@linux-foundation.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).