From: Roland Dreier <rdreier@cisco.com>
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] infiniband: remove __constant_{endian} uses
Date: Fri, 16 Jan 2009 13:59:25 -0800 [thread overview]
Message-ID: <ada4ozyewua.fsf@cisco.com> (raw)
In-Reply-To: <1232065920.11986.3.camel@brick> (Harvey Harrison's message of "Thu, 15 Jan 2009 16:32:00 -0800")
> Roland, the necessary byteorder rework is now in -linus mainline
> and all arches have moved over, I'm starting to remove the uses
> of the __constant_* helpers now that they are equivalent.
This looks good, thanks. I assume the expectation is that this should
be queued for the next merge window?
Code generation should be unaffected, right?
- R.
next prev parent reply other threads:[~2009-01-16 21:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 0:32 [PATCH] infiniband: remove __constant_{endian} uses Harvey Harrison
2009-01-16 21:59 ` Roland Dreier [this message]
2009-01-16 22:02 ` Harvey Harrison
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=ada4ozyewua.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=harvey.harrison@gmail.com \
--cc=linux-kernel@vger.kernel.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