On 7/14/05, Dave Airlie <[email protected]> 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
[email protected]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |