From: Jeff Dike <jdike@addtoit.com>
To: Jiri Olsa <olsajiri@gmail.com>
Cc: uml-devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] [PATCH] um: include/asm/arch link creation change
Date: Thu, 22 Nov 2007 09:44:04 -0500 [thread overview]
Message-ID: <20071122144404.GB4813@c2.user-mode-linux.org> (raw)
In-Reply-To: <47456321.2080600@gmail.com>
On Thu, Nov 22, 2007 at 12:08:17PM +0100, Jiri Olsa wrote:
> it works for me to use the HEADER_ARCH instead of the SUBARCH
Thanks - this is already in -mm, it just needs to get to mainline.
Jeff
--
Work email - jdike at linux dot intel dot com
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2007-11-22 14:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-22 11:08 [uml-devel] [PATCH] um: include/asm/arch link creation change Jiri Olsa
2007-11-22 14:44 ` Jeff Dike [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=20071122144404.GB4813@c2.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=olsajiri@gmail.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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.