From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756546AbYILDEz (ORCPT ); Thu, 11 Sep 2008 23:04:55 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751666AbYILDEl (ORCPT ); Thu, 11 Sep 2008 23:04:41 -0400 Received: from sj-iport-1.cisco.com ([171.71.176.70]:15866 "EHLO sj-iport-1.cisco.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751298AbYILDEk (ORCPT ); Thu, 11 Sep 2008 23:04:40 -0400 From: Roland Dreier To: Larry Finger Cc: Steven Noonan , LKML , wireless Subject: Re: I need help with a sparse warning References: <48C9D040.8010107@lwfinger.net> <48C9DACE.5040308@lwfinger.net> X-Message-Flag: Warning: May contain useful information Date: Thu, 11 Sep 2008 20:04:38 -0700 In-Reply-To: <48C9DACE.5040308@lwfinger.net> (Larry Finger's message of "Thu, 11 Sep 2008 21:58:22 -0500") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-OriginalArrivalTime: 12 Sep 2008 03:04:38.0807 (UTC) FILETIME=[4B48CA70:01C91484] Authentication-Results: sj-dkim-4; header.From=rdreier@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; ); Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > This one gets rid of the sparse warning. > > priv->rx_mtu = le16_to_cpu((__le16 __force) > bootrec->data[10]); Yes but does it actually work on both big and little endian systems? (See my previous email) - R.