From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
airlied@linux.ie, akpm <akpm@linux-foundation.org>
Subject: Re: [PATCH/RFC] video gfx: merge kconfig menus
Date: Sat, 29 Sep 2007 08:12:11 +0800 [thread overview]
Message-ID: <1191024731.5273.6.camel@daplas> (raw)
In-Reply-To: <20070924232536.b1123359.randy.dunlap@oracle.com>
On Mon, 2007-09-24 at 23:25 -0700, Randy Dunlap wrote:
> Is there some reason that we don't put all video gfx config in one
> place? Is the split just historical, based on subdirectory locations,
> or is there a bigger reason for it?
Just historical, based on subdirectory locations. Someone did attempt to
move the drm subdirectory under the video subdirectory during the 2.5
era but it was rejected.
Anyway, I'm fine with this too.
Tony
prev parent reply other threads:[~2007-09-29 0:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 6:25 [PATCH/RFC] video gfx: merge kconfig menus Randy Dunlap
2007-09-25 8:42 ` Dave Airlie
2007-09-29 0:12 ` Antonino A. Daplas [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=1191024731.5273.6.camel@daplas \
--to=adaplas@gmail.com \
--cc=airlied@linux.ie \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.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