From: Pavel Machek <pavel@ucw.cz>
To: Greg KH <greg@kroah.com>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: staging: where to put system-wide includes
Date: Sat, 17 Oct 2009 20:26:18 +0200 [thread overview]
Message-ID: <20091017182618.GD16532@elf.ucw.cz> (raw)
In-Reply-To: <20091008150010.GA11977@kroah.com>
On Thu 2009-10-08 08:00:10, Greg KH wrote:
> On Thu, Oct 08, 2009 at 01:28:18PM +0200, Pavel Machek wrote:
> > Hi!
> >
> > In staging, I need some includes that will become "system-wide" at the
> > end.
> >
> > Is it acceptable to create drivers/staging/include/linux (and
> > friends), and then use -I magic to include those headers?
>
> No, keep them in the subdir for the drivers you are adding please and
> reference them by the location directly, no -I magic.
That will make moving drivers to final place "interesting", but I'll
do as you wish.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-10-17 18:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-08 11:28 staging: where to put system-wide includes Pavel Machek
2009-10-08 15:00 ` Greg KH
2009-10-17 18:26 ` Pavel Machek [this message]
2009-10-08 18:40 ` Christoph Hellwig
2009-10-09 20:38 ` Pavel Machek
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=20091017182618.GD16532@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=greg@kroah.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