All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harvey Harrison <harvey.harrison@gmail.com>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Kyle McMartin <kyle@mcmartin.ca>,
	LKML <linux-kernel@vger.kernel.org>,
	"ralf@linux-mips.org" <ralf@linux-mips.org>,
	Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
Subject: Re: [PATCH 14/20] parisc: use the new byteorder headers
Date: Fri, 01 Aug 2008 22:52:27 -0700	[thread overview]
Message-ID: <1217656347.5846.9.camel@brick> (raw)
In-Reply-To: <20080801231807.GA26550@colo.lackof.org>

On Fri, 2008-08-01 at 17:18 -0600, Grant Grundler wrote:
> On Fri, Aug 01, 2008 at 02:23:37PM -0700, Harvey Harrison wrote:
> ...
> > > Should this only be defined if BITS_PER_LONG is <=32  ?
> > 
> > The new byteorder headers only uses this if no __arch_swab64 is defined.
> > 
> > Further down in the parisc version, an __arch_swab64 is defined in the
> > BITS_PER_LONG >=32 case, making this moot.
> 
> Ok.
> 
> ...
> > Other than the endianness, any other concerns?
> 
> Have you had a chance to test this?

le-only personally (X86-32).

> Or can you point me at another big endian arch that has similar 
> use of header files that has been successfully tested?

AVR32 got a maintainer ack, I'm assuming that was tested.  It's not
functionally any different than the existing code really, other
than allowing compile-time folding in the cpu_to_{endian} helpers.

Mips was also acked, but that can be little or big endian.

> 
> I can arrange for access to parisc HW if you have time/interest
> in testing this yourself.

Sure, drop me a note.

Harvey


  reply	other threads:[~2008-08-04  6:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-18  0:09 [PATCH 14/20] parisc: use the new byteorder headers Harvey Harrison
2008-08-01 16:06 ` Grant Grundler
2008-08-01 21:23   ` Harvey Harrison
2008-08-01 23:18     ` Grant Grundler
2008-08-02  5:52       ` Harvey Harrison [this message]
2008-08-02 18:03       ` 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=1217656347.5846.9.camel@brick \
    --to=harvey.harrison@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=grundler@parisc-linux.org \
    --cc=haavard.skinnemoen@atmel.com \
    --cc=kyle@mcmartin.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ralf@linux-mips.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 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.