[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1965688.fPKEQJnVvJ@dtor-d630.eng.vmware.com>
Date: Wed, 22 Aug 2012 14:45:35 -0700
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: Linus Walleij <linus.walleij@...aro.org>
Cc: Christopher Heiny <cheiny@...aptics.com>,
"Rafael J. Wysocki" <rjw@...k.pl>,
Jean Delvare <khali@...ux-fr.org>,
Linux Kernel <linux-kernel@...r.kernel.org>,
Linux Input <linux-input@...r.kernel.org>,
Allie Xiong <axiong@...aptics.com>,
William Manson <wmanson@...aptics.com>,
Peichen Chang <peichen.chang@...aptics.com>,
Joerie de Gram <j.de.gram@...il.com>,
Wolfram Sang <w.sang@...gutronix.de>,
Mathieu Poirier <mathieu.poirier@...aro.org>,
Linus Walleij <linus.walleij@...ricsson.com>,
Naveen Kumar Gaddipati <naveen.gaddipati@...ricsson.com>,
Henrik Rydberg <rydberg@...omail.se>
Subject: Re: [RFC PATCH 1/17] input: RMI4 public header file and documentation.
On Wednesday, August 22, 2012 09:08:00 PM Linus Walleij wrote:
> On Sat, Aug 18, 2012 at 12:17 AM, Christopher Heiny
> <cheiny@...aptics.com> wrote:
>
> > +/* Helper fn to convert a byte array representing a short in the RMI
> > + * endian-ness to a short in the native processor's specific endianness.
Is RMI-endiannes different from BE and LE (joking)? Please simply state what
on-wire endianness is and use xx_to_cpu() or cpu_to_xx() as needed. I think I
mentioned it about a year ago already...
Thanks.
--
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists