All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@osdl.org>
To: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@hp.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Fix blatant non-archdep'isms... need help with build env change?
Date: Mon, 12 Sep 2005 17:23:25 -0700	[thread overview]
Message-ID: <20050913002325.GS7901@shell0.pdx.osdl.net> (raw)
In-Reply-To: <516F50407E01324991DD6D07B0531AD5695A20@cacexc12.americas.cpqcorp.net>

* Magenheimer, Dan (HP Labs Fort Collins) (dan.magenheimer@hp.com) wrote:
> The problem files (in sparse/include/asm-xen):

I hit some of these as well.

> - synch_bitops.h: explicitly includes
>   asm-i386/synch_bitops.h, should include
>   <asm-xen/asm/synch_bitops.h>

I wondered about that.  Does that mean you have implementation of this,
or it it unnecessary on ia64?

> - hypervisor.h: about half of this header is
>   generic and half is x86-specific.  Should
>   include <asm-xen/asm/hypervisor.h> for
>   arch-dep code.

There's already arch specific files (for hypercall), I wonder if they
could be reused?

  reply	other threads:[~2005-09-13  0:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-12 23:25 Fix blatant non-archdep'isms... need help with build env change? Magenheimer, Dan (HP Labs Fort Collins)
2005-09-13  0:23 ` Chris Wright [this message]
2005-09-13 13:18   ` Dan Magenheimer (sent by Nabble.com)
2005-09-13 10:32 ` Keir Fraser
2005-09-13 13:16   ` Dan Magenheimer (sent by Nabble.com)
  -- strict thread matches above, loose matches on Subject: below --
2005-09-13 22:22 Magenheimer, Dan (HP Labs Fort Collins)

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=20050913002325.GS7901@shell0.pdx.osdl.net \
    --to=chrisw@osdl.org \
    --cc=dan.magenheimer@hp.com \
    --cc=xen-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.