From: "H. Peter Anvin" <hpa@transmeta.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Andrzej Krzysztofowicz <ankry@green.mif.pg.gda.pl>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
kernel list <linux-kernel@vger.kernel.org>,
Andries.Brouwer@cwi.nl
Subject: Re: iso9660 endianness cleanup patch
Date: Tue, 01 May 2001 14:06:41 -0700 [thread overview]
Message-ID: <3AEF2561.943849DF@transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.31.0105011358220.2667-100000@penguin.transmeta.com>
Linus Torvalds wrote:
>
> On Tue, 1 May 2001, H. Peter Anvin wrote:
> >
> > Oh bother, you're right of course. We need some kind of standardized
> > macro for indirecting through a potentially unaligned pointer.
>
> No we don't - because it already exists.
>
> It's called "get_unaligned()".
>
Well, we presumably do need it since it's there. I *did* correct this
brain fault of mine a few hours ago.
Note that it might still be an idea to have get_unaligned_le32() & co...
on some machines le32_to_cpu(get_unaligned()) could potentially be a lot
more painful than it needs to be.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
next prev parent reply other threads:[~2001-05-01 21:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-01 14:40 iso9660 endianness cleanup patch Andrzej Krzysztofowicz
2001-05-01 18:16 ` H. Peter Anvin
2001-05-01 18:43 ` H. Peter Anvin
2001-05-01 18:48 ` FIXED " H. Peter Anvin
2001-05-01 20:44 ` Alan Cox
2001-05-01 20:59 ` Linus Torvalds
2001-05-01 21:06 ` H. Peter Anvin [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-01 5:30 H. Peter Anvin
2001-05-01 6:14 ` Linus Torvalds
2001-05-01 6:18 ` H. Peter Anvin
2001-05-01 20:21 ` Pavel Machek
2001-05-04 1:51 ` Albert D. Cahalan
2001-05-04 4:59 ` Mike Galbraith
2001-05-01 6:37 ` Albert D. Cahalan
2001-05-01 9:52 ` Tim Riker
2001-05-02 8:52 ` Martin Dalecki
2001-05-02 16:03 ` H. Peter Anvin
2001-05-03 21:59 ` Pavel Machek
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=3AEF2561.943849DF@transmeta.com \
--to=hpa@transmeta.com \
--cc=Andries.Brouwer@cwi.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ankry@green.mif.pg.gda.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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