linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jingoo Han <jg1.han@samsung.com>
To: 'Tomi Valkeinen' <tomi.valkeinen@ti.com>,
	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>,
	'Jingoo Han' <jg1.han@samsung.com>
Subject: Re: [PATCH RFC 3/3] video: Kconfig: move drm and fb into separate menus
Date: Mon, 17 Feb 2014 01:55:19 +0000	[thread overview]
Message-ID: <000e01cf2b83$4f7a29b0$ee6e7d10$%han@samsung.com> (raw)
In-Reply-To: <1392376711-11290-3-git-send-email-tomi.valkeinen@ti.com>

On Friday, February 14, 2014 8:19 PM, Tomi Valkeinen wrote:
> 
> At the moment the "Device Drivers / Graphics support" kernel config page
> looks rather messy, with DRM and fbdev driver selections on the same
> page, some on the top level Graphics support page, some under their
> respective subsystems.
> 
> If I'm not mistaken, this is caused by the drivers depending on other
> things than DRM or FB, which causes Kconfig to arrange the options in
> not-so-neat manner.
> 
> Both DRM and FB have a main menuconfig option for the whole DRM or FB
> subsystem. Optimally, this would be enough to arrange all DRM and FB
> options under the respective subsystem, but for whatever reason this
> doesn't work reliably.
> 
> This patch adds an explicit submenu for DRM and FB, making it much
> clearer which options are related to FB, and which to DRM.
> 
> Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>

Reviewed-by: Jingoo Han <jg1.han@samsung.com>

I tested this patch. Menu becomes clearer!
Thanks.

Best regards,
Jingoo Han

> ---
>  drivers/video/Kconfig | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/drivers/video/Kconfig b/drivers/video/Kconfig
> index f0f26a0b746e..70d174090a54 100644
> --- a/drivers/video/Kconfig
> +++ b/drivers/video/Kconfig
> @@ -21,9 +21,13 @@ source "drivers/gpu/vga/Kconfig"
> 
>  source "drivers/gpu/host1x/Kconfig"
> 
> +menu "Direct Rendering Manager"
>  source "drivers/gpu/drm/Kconfig"
> +endmenu
> 
> +menu "Framebuffer Devices"
>  source "drivers/video/fbdev/Kconfig"
> +endmenu
> 
>  source "drivers/video/backlight/Kconfig"
> 
> --
> 1.8.3.2



  reply	other threads:[~2014-02-17  1:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1392376711-11290-1-git-send-email-tomi.valkeinen@ti.com>
2014-02-14 11:18 ` [PATCH RFC 2/3] fbdev: move fbdev core files to separate directory Tomi Valkeinen
2014-02-14 12:27   ` Geert Uytterhoeven
2014-02-14 12:31     ` Tomi Valkeinen
2014-02-17  1:51   ` Jingoo Han
2014-02-14 11:18 ` [PATCH RFC 3/3] video: Kconfig: move drm and fb into separate menus Tomi Valkeinen
2014-02-17  1:55   ` Jingoo Han [this message]
     [not found] ` <CAF6AEGvGBhBVQQ3_M-N=XhM+kOh_VZ=7QUQ3gUxJ8-ept7++cQ@mail.gmail.com>
2014-02-14 15:07   ` [PATCH RFC 1/3] video: move fbdev to drivers/video/fbdev Laurent Pinchart

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='000e01cf2b83$4f7a29b0$ee6e7d10$%han@samsung.com' \
    --to=jg1.han@samsung.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=geert@linux-m68k.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=plagnioj@jcrosoft.com \
    --cc=tomi.valkeinen@ti.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 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).