From: Rusty Russell <rusty@rustcorp.com.au>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
virtualization@lists.osdl.org, ak@suse.de
Subject: Re: [patch 4/9] lguest: the asm offsets
Date: Thu, 10 May 2007 10:09:39 +1000 [thread overview]
Message-ID: <1178755780.7286.175.camel@localhost.localdomain> (raw)
In-Reply-To: <20070509204613.GA10336@uranus.ravnborg.org>
On Wed, 2007-05-09 at 22:46 +0200, Sam Ravnborg wrote:
> On Wed, May 09, 2007 at 02:51:36AM -0700, akpm@linux-foundation.org wrote:
> > From: Rusty Russell <rusty@rustcorp.com.au>
> >
> > This is the structure offsets required by lg.ko's switcher.S.
> >
> > Unfortunately we don't have infrastructure for private asm-offsets
> > creation.
> Someone maybe it was Oleg? did an OK job to abstract out asm-offset
> generation. I asked to have it rebased but never heard anything back.
>
> I would like to get this generic approach in and then let lguest use it.
> But I do not see this as a reason to hold back inclusion in -linus.
Hi Sam,
Yeah, I never heard back either. And I'm reluctant to try to fix it
myself: I've never managed to patch the build system without causing you
to rewrite it better 8)
> But could we please get rid of the "../../../" in the include....
Sure: but how? It's a private internal include for the lg.ko module.
Thanks!
Rusty.
next prev parent reply other threads:[~2007-05-10 0:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 9:51 [patch 4/9] lguest: the asm offsets akpm
2007-05-09 20:46 ` Sam Ravnborg
2007-05-10 0:09 ` Rusty Russell [this message]
2007-06-11 12:49 ` Oleg Verych
2007-06-11 12:59 ` Sam Ravnborg
2007-06-12 10:31 ` [patch] kbuild: remember ARCH in the object directory Oleg Verych
2007-06-12 15:04 ` Randy Dunlap
2007-06-12 16:12 ` Randy Dunlap
2007-06-12 17:19 ` Oleg Verych
2007-06-12 18:09 ` Sam Ravnborg
2007-06-13 2:12 ` [kbuild-devel] " H. Peter Anvin
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=1178755780.7286.175.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=virtualization@lists.osdl.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