From: Lachlan McIlroy <lachlan@sgi.com>
To: Timothy Shimmin <tes@sgi.com>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: endianess macros
Date: Tue, 19 Aug 2008 18:17:52 +1000 [thread overview]
Message-ID: <48AA81B0.9000403@sgi.com> (raw)
In-Reply-To: <48AA6844.7000203@sgi.com>
I just pushed it in.
Timothy Shimmin wrote:
> Christoph Hellwig wrote:
>> This commit:
>>
>> commit 413d57c9907c72ed608df2be72ef8ed13a3eeb46
>> Author: Marcin Slusarz <marcin.slusarz@gmail.com>
>> Date: Wed Feb 13 15:03:29 2008 -0800
>>
>> xfs: convert beX_add to beX_add_cpu (new common API)
>>
>> remove beX_add functions and replace all uses with beX_add_cpu
>>
>> which is in Linus tree never made it to the oss cvs tree. It's doing
>> this little change all over the place, so having it in both trees would
>> be really useful..
>>
>
> Yes, thanks I'll add this one into dev.
> I'd really like to start changing stuff to minimise our
> cvs/mainline differences.
> It's time I did the diff like you and Lachlan have done :)
>
> --Tim
>
>
>
prev parent reply other threads:[~2008-08-19 8:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080814180856.GB3087@infradead.org>
2008-08-19 6:29 ` endianess macros Timothy Shimmin
2008-08-19 8:17 ` Lachlan McIlroy [this message]
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=48AA81B0.9000403@sgi.com \
--to=lachlan@sgi.com \
--cc=hch@infradead.org \
--cc=tes@sgi.com \
--cc=xfs@oss.sgi.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