From: Harvey Harrison <harvey.harrison@gmail.com>
To: Roland Dreier <rdreier@cisco.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] infiniband: remove __constant_{endian} uses
Date: Fri, 16 Jan 2009 14:02:22 -0800 [thread overview]
Message-ID: <1232143342.6737.1.camel@brick> (raw)
In-Reply-To: <ada4ozyewua.fsf@cisco.com>
On Fri, 2009-01-16 at 13:59 -0800, Roland Dreier wrote:
> > 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?
>
Your call, it's only a name change, the implementation on the back end is
now the same for both, so I expect the generated code to be identical.
But it is obviously not urgent, so holding for 2.6.30 is just fine.
Harvey
prev parent reply other threads:[~2009-01-16 22:03 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
2009-01-16 22:02 ` Harvey Harrison [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=1232143342.6737.1.camel@brick \
--to=harvey.harrison@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdreier@cisco.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