linux-kernel - Re: [PATCH 14/20] parisc: use the new byteorder headers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 2 Aug 2008 11:03:49 -0700
From:	"Harvey Harrison" <harvey.harrison@...il.com>
To:	"Grant Grundler" <grundler@...isc-linux.org>
Cc:	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Kyle McMartin" <kyle@...artin.ca>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 14/20] parisc: use the new byteorder headers

My reply yesterday didn't seem to make it out.

On Fri, Aug 1, 2008 at 4:18 PM, Grant Grundler
<grundler@...isc-linux.org> wrote:
> On Fri, Aug 01, 2008 at 02:23:37PM -0700, Harvey Harrison wrote:
>> 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.

I'll have intermittant connection for the next week, so there might be
a few days before I can reply.

Harvey
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/