From: Jon Smirl <jonsmirl@gmail.com>
To: Dave Airlie <airlied@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: moving DRM header files
Date: Thu, 14 Jul 2005 09:17:39 -0400 [thread overview]
Message-ID: <9e47339105071406177dc4dad6@mail.gmail.com> (raw)
In-Reply-To: <21d7e9970507132209e7ac477@mail.gmail.com>
On 7/14/05, Dave Airlie <airlied@gmail.com> wrote:
> > > I'm thinking include/linux/drm/
> > > but include/linux would also be possible.
> > >
> > > Any suggestions or ideas?
> >
> > If you're in a mood to move things, how about moving drivers/char/drm
> > to drivers/video/drm.
>
> But that has little point beyond aesthetics... moving the header files
> is for a reason that I want them to start appearing in userspace
> includeable places.. as part of the cleanup for libdrm..
>
> Moving c files internally in the kernel provides no real benefit over
> not moving them..
When you start merging DRM and fbdev you will be able to use relative
paths that are closer together. For example #include
"../char/drm/drmP.h" versus "#include "drm/drmP.h" for internal
headers.
DRM and fbdev need to be moved next to each other in kconfig too if
they start depending on each other. It if hard to figure out that a
video option might not be visible because the char/drm/option is not
turned on.
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2005-07-14 13:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-14 4:04 moving DRM header files Dave Airlie
2005-07-14 4:22 ` Jon Smirl
2005-07-14 4:25 ` Jon Smirl
2005-07-14 5:09 ` Dave Airlie
2005-07-14 13:17 ` Jon Smirl [this message]
2005-07-14 18:53 ` Sam Ravnborg
2005-07-14 7:37 ` Arjan van de Ven
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=9e47339105071406177dc4dad6@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=airlied@gmail.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.