From: Harvey Harrison <harvey.harrison@gmail.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
sfr@canb.auug.org.au
Subject: Re: byteorder headers on parisc
Date: Tue, 09 Dec 2008 15:12:37 -0800 [thread overview]
Message-ID: <1228864357.5480.2.camel@brick> (raw)
In-Reply-To: <20081209135714.GB7785@x200.localdomain>
On Tue, 2008-12-09 at 16:57 +0300, Alexey Dobriyan wrote:
> May I politely ask how this was compiled-tested?
It wasn't. I missed the usage of the internal __fswabXX on parisc,
Kyle already contected me yesterday about this and worked out
a fix.
Harvey
next prev parent reply other threads:[~2008-12-09 23:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-09 7:52 linux-next: Tree for December 9 Stephen Rothwell
2008-12-09 8:53 ` Al Viro
2008-12-09 13:57 ` byteorder headers on parisc Alexey Dobriyan
2008-12-09 23:12 ` Harvey Harrison [this message]
2008-12-09 23:34 ` linux-next: Tree for December 9 Andrew Morton
2008-12-10 0:06 ` Kay Sievers
2008-12-10 0:15 ` Andrew Morton
2008-12-10 0:31 ` Kay Sievers
2008-12-10 1:30 ` Andrew Morton
2008-12-10 1:36 ` Kay Sievers
2008-12-10 1:42 ` NeilBrown
2008-12-10 1:58 ` Andrew Morton
2008-12-10 19:16 ` Andrew Morton
2008-12-10 22:15 ` Neil Brown
2008-12-10 11:57 ` [BUG] linux-next: 20081209 - kernel bug at __rcu_process_callbacks, while booting up Kamalesh Babulal
2008-12-10 14:54 ` Paul E. McKenney
2008-12-10 16:30 ` Kamalesh Babulal
2008-12-10 17:53 ` Paul E. McKenney
2008-12-10 18:09 ` Kamalesh Babulal
2008-12-10 18:33 ` Paul E. McKenney
2008-12-12 19:40 ` Kamalesh Babulal
2008-12-12 22:16 ` Paul E. McKenney
2008-12-16 14:30 ` Kamalesh Babulal
2008-12-16 14:37 ` Jens Axboe
2008-12-17 11:12 ` Kamalesh Babulal
2008-12-17 11:18 ` Jens Axboe
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=1228864357.5480.2.camel@brick \
--to=harvey.harrison@gmail.com \
--cc=adobriyan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).