public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Harvey Harrison <harvey.harrison@gmail.com>
To: Piet Delaney <piet.delaney@tensilica.com>
Cc: Chris Zankel <chris@zankel.net>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Marc Gauthier <marc@tensilica.com>,
	Joe Taylor <joetayloremail@gmail.com>,
	linux-xtensa@linux-xtensa.org,
	Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [PATCH 10/10] xtensa: use the new byteorder headers - Merged with your previous xtensa-next and will remerge shortly.
Date: Fri, 07 Nov 2008 19:38:01 -0800	[thread overview]
Message-ID: <1226115481.11596.63.camel@brick> (raw)
In-Reply-To: <491500C0.90407@tensilica.com>

On Fri, 2008-11-07 at 19:00 -0800, Piet Delaney wrote:
> Hi Chris:
> 
>    I've merged your recent xtensa-next with our 2.6.24-smp repo.
> It seems to work fine and I'm in the process of cleaning it
> up a bit and adding preliminary XTENSA kgdb support.

2.6.24?  In that case you probably don't have include/linux/byteorder.h,
or include/linux/swab.h which would explain your byteorder problems.

Or is that a typo in the version numbers?

You should be able to just pull those two headers from Linus' tree
and drop them in, there is no dependencies other than those two
headers.

If it is some other problem, let me know and I'll look into it.

Harvey


  reply	other threads:[~2008-11-08  3:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-05 18:35 [PATCH 10/10] xtensa: use the new byteorder headers Harvey Harrison
2008-11-06 17:59 ` Chris Zankel
2008-11-08  3:00   ` [PATCH 10/10] xtensa: use the new byteorder headers - Merged with your previous xtensa-next and will remerge shortly Piet Delaney
2008-11-08  3:38     ` Harvey Harrison [this message]
2008-11-09  3:55       ` Piet Delaney
2008-11-14  8:13         ` Piet Delaney
2008-11-14 16:33           ` Harvey Harrison

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=1226115481.11596.63.camel@brick \
    --to=harvey.harrison@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=chris@zankel.net \
    --cc=chuck.lever@oracle.com \
    --cc=joetayloremail@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xtensa@linux-xtensa.org \
    --cc=marc@tensilica.com \
    --cc=piet.delaney@tensilica.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox