From: Arnd Bergmann <arnd@arndb.de>
To: Avi Kivity <avi@redhat.com>
Cc: Mark McLoughlin <markmc@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH] kvm: user: include arch specific headers from $(KERNELDIR)
Date: Thu, 14 May 2009 18:07:51 +0200 [thread overview]
Message-ID: <200905141807.52142.arnd@arndb.de> (raw)
In-Reply-To: <4A0C3EF4.3080708@redhat.com>
On Thursday 14 May 2009, Avi Kivity wrote:
> I usually add a readlink -f in there due to my innate fear of relative
> directories and cd.
There is one already in the only place where this gets used:
KERNELDIR=$(readlink -f $kerneldir)
It also gets shown in the configure --help output, but I suppose
showing the relative path there may be helpful because of its
brevity.
Arnd <><
next prev parent reply other threads:[~2009-05-14 16:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 8:32 [PATCH] kvm: user: include arch specific headers from $(KERNELDIR) Mark McLoughlin
2009-05-13 21:57 ` Arnd Bergmann
2009-05-14 7:52 ` Mark McLoughlin
2009-05-14 8:02 ` Avi Kivity
2009-05-14 15:49 ` Arnd Bergmann
2009-05-14 15:55 ` Avi Kivity
2009-05-14 16:07 ` Arnd Bergmann [this message]
2009-05-17 22:18 ` Avi Kivity
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=200905141807.52142.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=markmc@redhat.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