From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Randy Dunlap <rdunlap@infradead.org>,
<linux-fbdev@vger.kernel.org>, <dri-devel@lists.freedesktop.org>,
<linux-kernel@vger.kernel.org>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
David Airlie <airlied@linux.ie>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH 0/3] Reorder drivers/video directory
Date: Wed, 5 Mar 2014 08:32:40 +0200 [thread overview]
Message-ID: <5316C508.2000402@ti.com> (raw)
In-Reply-To: <531627D6.6060007@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 1907 bytes --]
On 04/03/14 21:21, Randy Dunlap wrote:
>> I have pushed this to my for-next branch. Let's see what happens... At
>> least I'm able to merge the current linux-next without any conflicts.
>
> Thanks, I'm looking at this change in linux-next now.
>
> EXYNOS_VIDEO seems to be a little bit odd. Can you clarify that for me?
> (This is not a change that you introduced.)
>
>
> In particular, under Graphics support, select Framebuffer Devices.
> This lists:
> Support for frame buffer devices -->
> Exynos Video driver support
>
> It appears to me that Exynos either is a Framebuffer Device and should depend
> on FB like the other drivers here do OR (actually XOR) it is not a frame buffer
> device and it should not be listed here.
>
> Then once that is cleared up :), we don't need 2 levels of menu to get to the
> list of FB drivers -- i.e., one of those levels can be removed.
There are others. For my config, I have:
{*} Support for frame buffer devices --->
<M> OMAP2+ Display Subsystem support --->
[ ] Exynos Video driver support ----
< > Solomon SSD1307 framebuffer support
I didn't want to start fixing those at the moment, as I have no idea
about exynos or solomon, and I wanted to just try to do the reorder,
without any other changes.
I agree that there's something wrong with the items. For the OMAP DSS,
there are non-fbdev related items under that menu, used also by omapdrm.
So it should probably be split into different components.
> Oh, and if you keep the new menu item "Framebuffer Devices", please spell it
> like the other entry (Frame Buffer).
Ok, fixed.
> Other than those nits, I like this change very much. Thanks.
Thanks. After pushing this to for-next, I'm getting compile error
reports from Fengguang and Stephen. Let's see if I manage to avoid
those... This is not the easiest change to manage.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
next prev parent reply other threads:[~2014-03-05 6:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 11:54 [PATCH 0/3] Reorder drivers/video directory Tomi Valkeinen
2014-02-27 11:54 ` [PATCH 1/3] video: move fbdev to drivers/video/fbdev Tomi Valkeinen
2014-02-27 11:54 ` [PATCH 2/3] fbdev: move fbdev core files to separate directory Tomi Valkeinen
2014-02-27 11:54 ` [PATCH 3/3] video: Kconfig: move drm and fb into separate menus Tomi Valkeinen
2014-02-27 18:16 ` [PATCH 0/3] Reorder drivers/video directory Randy Dunlap
2014-02-28 7:07 ` Tomi Valkeinen
2014-02-28 8:03 ` Geert Uytterhoeven
2014-03-03 8:45 ` Tomi Valkeinen
2014-03-04 19:21 ` Randy Dunlap
2014-03-05 6:32 ` Tomi Valkeinen [this message]
2014-03-04 9:50 ` Daniel Vetter
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=5316C508.2000402@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=airlied@linux.ie \
--cc=akpm@linux-foundation.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=plagnioj@jcrosoft.com \
--cc=rdunlap@infradead.org \
--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