From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: linux-fbdev@vger.kernel.org,
Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm: Remove two-level menu in Kconfig
Date: Mon, 10 Aug 2015 11:54:36 +0000 [thread overview]
Message-ID: <55C890FC.2090809@ti.com> (raw)
In-Reply-To: <20150810114718.GU17734@phenom.ffwll.local>
[-- Attachment #1: Type: text/plain, Size: 1183 bytes --]
On 10/08/15 14:47, Daniel Vetter wrote:
> On Mon, Aug 10, 2015 at 01:32:08PM +0300, Tomi Valkeinen wrote:
>>
>>
>> On 07/08/15 19:10, Thierry Reding wrote:
>>> From: Thierry Reding <treding@nvidia.com>
>>>
>>> The Direct Rendering Manager Kconfig option is already a separate menu,
>>> so remove the extra level to make it easier to navigate.
>>>
>>> Signed-off-by: Thierry Reding <treding@nvidia.com>
>>> ---
>>> drivers/video/Kconfig | 2 --
>>> 1 file changed, 2 deletions(-)
>>>
>>> diff --git a/drivers/video/Kconfig b/drivers/video/Kconfig
>>> index 8bf495ffb020..e0606c01e8ac 100644
>>> --- a/drivers/video/Kconfig
>>> +++ b/drivers/video/Kconfig
>>> @@ -22,9 +22,7 @@ source "drivers/gpu/vga/Kconfig"
>>> source "drivers/gpu/host1x/Kconfig"
>>> source "drivers/gpu/ipu-v3/Kconfig"
>>>
>>> -menu "Direct Rendering Manager"
>>> source "drivers/gpu/drm/Kconfig"
>>> -endmenu
>>>
>>> menu "Frame buffer Devices"
>>> source "drivers/video/fbdev/Kconfig"
>>>
>>
>> Thanks, queued for 4.3.
>
> Oops failed to send out my usual mail, but I picked this already up in
> topic/drm-misc.
Ok, dropping this from fbdev tree.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-08-10 11:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 16:10 [PATCH] drm: Remove two-level menu in Kconfig Thierry Reding
2015-08-10 10:32 ` Tomi Valkeinen
2015-08-10 11:47 ` Daniel Vetter
2015-08-10 11:54 ` Tomi Valkeinen [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=55C890FC.2090809@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=plagnioj@jcrosoft.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).