From: Tristan Gingold <tgingold@free.fr>
To: Alex Williamson <alex.williamson@hp.com>
Cc: xen-ppc-devel <xen-ppc-devel@lists.xensource.com>,
xen-devel@lists.xensource.com,
Hollis Blanchard <hollisb@us.ibm.com>,
xen-ia64-devel@lists.xensource.com
Subject: Re: Re: [Xen-devel] Re: [Xen-changelog] [xen-unstable] [IA64] fix xencomm_handle_is_null().
Date: Thu, 16 Nov 2006 21:44:20 +0100 [thread overview]
Message-ID: <20061116204420.GC2568@saphi> (raw)
In-Reply-To: <1163700499.5529.9.camel@lappy>
On Thu, Nov 16, 2006 at 11:08:19AM -0700, Alex Williamson wrote:
> On Thu, 2006-11-16 at 09:55 -0600, Hollis Blanchard wrote:
> >
> > I think I'm missing something. Why did IA64 fork xencomm?
> >
> > I distinctly remember having conversations about sharing the code, which
> > is obviously the right thing to do.
>
> Because Tristan believed the resulting amount of shared code would
> actually be very small (1 file) and we wanted to get his work into the
> tree before he left Bull. We can still work to share as much as
> possible even with the code split. Thanks,
Indeed. Only asm/guest_access.h can be easily shared. Feel free to do it.
For the other files, sharing can't be easily done. We have slightly changed
the interface (we now have 3 ways: inline, mini and area). Furthermore
the translators are not very stable: bugs have been fixed recently.
Tristan.
next prev parent reply other threads:[~2006-11-16 20:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Gk8pJ-0007ef-Tr@xenbits.xensource.com>
2006-11-16 15:55 ` [Xen-changelog] [xen-unstable] [IA64] fix xencomm_handle_is_null() Hollis Blanchard
2006-11-16 18:08 ` Alex Williamson
2006-11-16 20:44 ` Tristan Gingold [this message]
2006-11-16 21:52 ` consolidated xencomm Hollis Blanchard
2006-11-17 0:14 ` [XenPPC] " Hollis Blanchard
2006-11-16 21:58 ` Hollis Blanchard
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=20061116204420.GC2568@saphi \
--to=tgingold@free.fr \
--cc=alex.williamson@hp.com \
--cc=hollisb@us.ibm.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-ia64-devel@lists.xensource.com \
--cc=xen-ppc-devel@lists.xensource.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 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.