From: Sam Ravnborg <sam@ravnborg.org>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: Dave Airlie <airlied@gmail.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: moving DRM header files
Date: Thu, 14 Jul 2005 18:53:25 +0000 [thread overview]
Message-ID: <20050714185325.GA8791@mars.ravnborg.org> (raw)
In-Reply-To: <9e47339105071406177dc4dad6@mail.gmail.com>
>
> 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.
No. Using relative include paths is not good. I will most probarly
not work with make O=.
Sam
next prev parent reply other threads:[~2005-07-14 17:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-14 4:04 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
2005-07-14 18:53 ` Sam Ravnborg [this message]
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=20050714185325.GA8791@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=airlied@gmail.com \
--cc=jonsmirl@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®