Received: by 2002:a25:e7d8:0:0:0:0:0 with SMTP id e207csp2097513ybh; Sun, 8 Mar 2020 22:04:36 -0700 (PDT) X-Google-Smtp-Source: ADFU+vsaK5n3FmD3QfLc41Xt5yZ7m0OTSlZBHdXycT97801zkLGF6/8kGmCwATE40a96j8rs8UV9 X-Received: by 2002:aca:534d:: with SMTP id h74mr4884598oib.173.1583730276290; Sun, 08 Mar 2020 22:04:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1583730276; cv=none; d=google.com; s=arc-20160816; b=GdHHNIV7uhMbjpC83WHNAHUz8E0zt+xtno+HvfxvyLVuLha3E74ThrJxWzrnMuhNGc CopcQ+oHAwYALtTZHYCqAs7nBhv4Vl9NbSORbXqD7fxWVrcP7LMi7WN5sNorsi70AocK AU/fmzi1xR/GpYJkxhjSsY5Uf5ru34/qBcXb+3THQho0Tk6U2MZ3D6whc3BykYtEcIfn Xxg3Q+JTw8ncT1h3C6Jb/WvmLLKKIqT3A8EIi2dGPQTYbCmAQ9ieWHDC1NPBIhf+lFC2 9AIxU5xdo1VzJN+BQK4rPVuMIzBP8U2pQk6WYl3LQTzCgnJ/FrzcV2fMGZu++URKdyLg f3jQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:from:subject:cc:to:message-id:date; bh=+n9SmInp7kOMPLKeqlDfSwlO3eBxwhKNhY5FELsVxu0=; b=g9nA46S+0msPnqGWT3BPfbEZnxNBwyrvnCflJ3YBoTgBPy4c0hq/Iz6gyfMM/GGR7Q S1/mx9hGegeosu1cK1BayPYgqPQkJqZdH24gVS3pa6ygiqiF9iHPv7dLDHqbsiMhC4P0 KTcbv3jimbafUGpZbQ86hH5YXM9ddVzkzFKmBNnCmMqsHq9QumtNBNdng18oepeXgUFV Lq8Cjl0yS4azkOkOTJBwHJQIxbkyRoFsMPMIVuaHQUSN5zKpvw/J7hJP5cRLn+Rauby+ Al6AZ7ep7OAVGwGyml4W8IPhY/6S7NiiViXDNuMmFn85xF20MPCKgePRLbZ3n+lGyIKc rbBw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id r12si3274917oic.246.2020.03.08.22.04.23; Sun, 08 Mar 2020 22:04:36 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726402AbgCIFEF (ORCPT + 99 others); Mon, 9 Mar 2020 01:04:05 -0400 Received: from shards.monkeyblade.net ([23.128.96.9]:54182 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725796AbgCIFEF (ORCPT ); Mon, 9 Mar 2020 01:04:05 -0400 Received: from localhost (unknown [IPv6:2601:601:9f00:477::3d5]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: davem-davemloft) by shards.monkeyblade.net (Postfix) with ESMTPSA id 4BFE6158B8427; Sun, 8 Mar 2020 22:04:04 -0700 (PDT) Date: Sun, 08 Mar 2020 22:04:03 -0700 (PDT) Message-Id: <20200308.220403.2013988891795466479.davem@davemloft.net> To: bay@hackerdom.ru Cc: oliver@neukum.org, gregkh@linuxfoundation.org, tglx@linutronix.de, info@metux.net, allison@lohutok.net, linux-usb@vger.kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] cdc_ncm: Implement the 32-bit version of NCM Transfer Block From: David Miller In-Reply-To: <20200305203318.8980-1-bay@hackerdom.ru> References: <20200305203318.8980-1-bay@hackerdom.ru> X-Mailer: Mew version 6.8 on Emacs 26.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Sun, 08 Mar 2020 22:04:04 -0700 (PDT) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Alexander Bersenev Date: Fri, 6 Mar 2020 01:33:16 +0500 > The NCM specification defines two formats of transfer blocks: with 16-bit > fields (NTB-16) and with 32-bit fields (NTB-32). Currently only NTB-16 is > implemented. > > This patch adds the support of NTB-32. The motivation behind this is that > some devices such as E5785 or E5885 from the current generation of Huawei > LTE routers do not support NTB-16. The previous generations of Huawei > devices are also use NTB-32 by default. > > Also this patch enables NTB-32 by default for Huawei devices. > > During the 2019 ValdikSS made five attempts to contact Huawei to add the > NTB-16 support to their router firmware, but they were unsuccessful. > > Signed-off-by: Alexander Bersenev Oliver et al., please review. Thank you.