From: Daniel Phillips <phillips@phunq.net>
To: Roland Dreier <rdreier@cisco.com>
Cc: tux3@tux3.org, Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [Tux3] Tux3 report: Tux3 Git tree available
Date: Sat, 14 Mar 2009 21:02:56 -0700 [thread overview]
Message-ID: <200903142102.56602.phillips@phunq.net> (raw)
In-Reply-To: <aday6vaqwtk.fsf@cisco.com>
On Thursday 12 March 2009, Roland Dreier wrote:
> > By the way, the endian comment in bitmap.c needs some loving:
> >
> > http://lxr.linux.no/linux+v2.6.28.7/lib/bitmap.c#L35
> >
> > The s390 file needs to be config-independent:
> >
> > - include/asm-s390/bitops.h
> > + arch/s390/include/asm/bitops.h
> >
> > and the ppc file is nowhere to be seen. I will put a driveby patch on
> > the to.do list.
>
> The ppc file is arch/powerpc/include/asm/bitops.h.
Ah right, so the commentary should just reference arch/ instead of
/..asm-<arch>. I am still hoping to hear an actual argument why little
endian bitops are "more natural" than big endian. I don't know of any
myself, either in terms of machine instructions, cycle times or
whatever.
Regards,
Daniel
next prev parent reply other threads:[~2009-03-15 4:03 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 16:25 Tux3 report: Tux3 Git tree available Daniel Phillips
2009-03-11 18:42 ` Andrew Morton
2009-03-12 5:38 ` [Tux3] " Daniel Phillips
2009-03-12 6:07 ` Andrew Morton
2009-03-12 8:33 ` Daniel Phillips
2009-03-12 8:47 ` Nick Piggin
2009-03-12 9:00 ` Daniel Phillips
2009-03-12 9:10 ` Nick Piggin
2009-03-12 10:15 ` Daniel Phillips
2009-03-12 11:03 ` Nick Piggin
2009-03-12 12:24 ` Daniel Phillips
2009-03-12 12:32 ` Matthew Wilcox
2009-03-12 12:45 ` Nick Piggin
2009-03-12 13:12 ` Daniel Phillips
2009-03-12 13:06 ` Daniel Phillips
2009-03-12 13:04 ` Nick Piggin
2009-03-12 13:59 ` Matthew Wilcox
2009-03-12 14:19 ` Nick Piggin
2009-03-15 3:24 ` Daniel Phillips
2009-03-15 3:50 ` Nick Piggin
2009-03-15 4:08 ` Daniel Phillips
2009-03-15 4:14 ` Nick Piggin
2009-03-15 2:41 ` Daniel Phillips
2009-03-15 3:45 ` Nick Piggin
2009-03-15 21:44 ` Theodore Tso
2009-03-15 22:41 ` Daniel Phillips
2009-03-16 10:32 ` Nick Piggin
2009-03-16 5:12 ` Dave Chinner
2009-03-16 6:38 ` Theodore Tso
2009-03-16 10:14 ` Nick Piggin
2009-03-12 17:06 ` Theodore Tso
2009-03-13 9:32 ` Nick Piggin
2009-03-12 17:00 ` OGAWA Hirofumi
2009-03-15 3:54 ` Daniel Phillips
2009-03-12 9:47 ` Sam Ravnborg
2009-03-12 10:25 ` Daniel Phillips
2009-03-12 15:30 ` Diego Calleja
2009-03-12 16:54 ` OGAWA Hirofumi
2009-03-15 3:36 ` Daniel Phillips
2009-03-15 4:26 ` OGAWA Hirofumi
2009-03-12 13:24 ` Andi Kleen
2009-03-12 21:24 ` [Tux3] " Daniel Phillips
2009-03-12 23:38 ` Andi Kleen
2009-03-15 3:03 ` Daniel Phillips
2009-03-12 21:02 ` Roland Dreier
2009-03-15 4:02 ` Daniel Phillips [this message]
2009-03-12 16:18 ` OGAWA Hirofumi
2009-03-12 20:02 ` Andrew Morton
2009-03-12 20:46 ` OGAWA Hirofumi
2009-03-15 3:58 ` Daniel Phillips
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=200903142102.56602.phillips@phunq.net \
--to=phillips@phunq.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdreier@cisco.com \
--cc=tux3@tux3.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox