From mboxrd@z Thu Jan 1 00:00:00 1970 From: Oliver Neukum Subject: Re: [PATCH net-next 08/19] net: usb: aqc111: Implement TX data path Date: Mon, 08 Oct 2018 16:07:53 +0200 Message-ID: <1539007673.10342.21.camel@suse.com> References: <65674cc0cd1b025d859b1b0a5410b21ca9f88176.1538734658.git.igor.russkikh@aquantia.com> <20181006011325.GB32455@lunn.ch> <3d55fcaf-3297-f315-b258-2887d5a64cf6@aquantia.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: Dmitry Bezrukov , "David S . Miller" , "linux-usb@vger.kernel.org" , "netdev@vger.kernel.org" To: Igor Russkikh , Andrew Lunn Return-path: Received: from mx2.suse.de ([195.135.220.15]:54774 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726056AbeJHV2k (ORCPT ); Mon, 8 Oct 2018 17:28:40 -0400 In-Reply-To: <3d55fcaf-3297-f315-b258-2887d5a64cf6@aquantia.com> Sender: netdev-owner@vger.kernel.org List-ID: On Mo, 2018-10-08 at 13:43 +0000, Igor Russkikh wrote: > > > + skb_push(skb, AQ_TX_HEADER_SIZE); > > > + cpu_to_le64s(&tx_hdr); > > > > Is that portable? tx_hdr is a structure of 2x u32 bitfields. What > > endian have you tested that one? > > > > You are right, this is wrong for BE hardware. > > We don't have such a hardware to check unfortunately. > Think its better to drop endianess conversions and declare > the driver as little endian only. > > Do you think that'll be acceptable? No. If worse comes to worse define it u64 and set the values manually. Regards Oliver