DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=subject:from:to:cc:in-reply-to:references:content-type:date
         :message-id:mime-version:x-mailer:content-transfer-encoding;
        b=keVJFAbVUUQh83vGhyav7nZojpPePqTi05hw56YFhYyjqoA9F4bJJ0SGw7/ZaMlUCi
         VtQSnDrN3LpSaYyUpwebC/ae6p04NxYH8WxCgpnJrw7IuendM77Y9ieKHG5pdl1bMCzV
         y8v+4T2Wzjk29fQpqopnTCGA8D8wEPimgC1ug=
Subject: Re: [PATCH] infiniband: remove __constant_{endian} uses
From: Harvey Harrison <harvey.harrison@gmail.com>
To: Roland Dreier <rdreier@cisco.com>
Cc: LKML <linux-kernel@vger.kernel.org>
In-Reply-To: <ada4ozyewua.fsf@cisco.com>
References: <1232065920.11986.3.camel@brick>  <ada4ozyewua.fsf@cisco.com>
Content-Type: text/plain
Date: Fri, 16 Jan 2009 14:02:22 -0800
Message-Id: <1232143342.6737.1.camel@brick>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 894
Lines: 23

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/