From: Rusty Russell <rusty@rustcorp.com.au>
To: "Bryan O'Sullivan" <bos@pathscale.com>
Cc: kai@tp1.ruhr-uni-bochum.de, sam@ravnborg.org, akpm@osdl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Get modpost to work properly with vmlinux in a different directory
Date: Mon, 22 Dec 2003 12:43:15 +1100 [thread overview]
Message-ID: <20031222124315.46a4268c.rusty@rustcorp.com.au> (raw)
In-Reply-To: <1071698186.10795.56.camel@serpentine.pathscale.com>
On Wed, 17 Dec 2003 13:56:27 -0800
Bryan O'Sullivan <bos@pathscale.com> wrote:
> This is pretty trivial. The current version of modpost breaks if
> invoked from outside the build tree. This patch fixes that, and
> simplifies the code a bit while it's at it.
Thanks, I've taken it. I'll push to Andrew once things have calmed down.
Thanks,
Rusty.
--
there are those who do and those who hang on and you don't see too
many doers quoting their contemporaries. -- Larry McVoy
prev parent reply other threads:[~2003-12-22 1:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-17 21:56 [PATCH] Get modpost to work properly with vmlinux in a different directory Bryan O'Sullivan
2003-12-22 1:43 ` Rusty Russell [this message]
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=20031222124315.46a4268c.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=akpm@osdl.org \
--cc=bos@pathscale.com \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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.