Received: by 2002:a25:e7d8:0:0:0:0:0 with SMTP id e207csp152496ybh; Wed, 11 Mar 2020 23:00:19 -0700 (PDT) X-Google-Smtp-Source: ADFU+vsyz+ab/xl7LIsX88qr/OnQyi96giVNHWLbOK2/7+PCLmnoq5eFqUjwum8JaiWShUYG0J0V X-Received: by 2002:aca:aa12:: with SMTP id t18mr1502946oie.95.1583992819110; Wed, 11 Mar 2020 23:00:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1583992819; cv=none; d=google.com; s=arc-20160816; b=bTxQRDz5E7k1wghEZjvh+An/I0P5D4TulIM8qANBboiMG5viVysvPnUhxA/lloxues 6P2LXZkCnFiaztE6wsItbX3XUmxYEaBIM0zI5fwkE4StsP+U2dWEihyWvG398wb55Rtt NNRL+dzYHG26uJwMqdw86rb5z1ExZ33sBNXUD1r2lA3uyR0mVx2Pj8HMRcywfwTJzsEz e+X79HIXbA/YO9G1enLZQ1L5ZtepkkIKYxLF8A2tKevwg6cTX1eLb8hHYTan5FeFnHyN iC/RrezOd5e4QhzxvH90m5MCelrgkyw+hKXXvTizNpI34yZ0ZoxigBElwR9Gl1cN0NEw df3w== 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=dmGgtYoM74Z2jLS6renC8RXaNtpyfB32b7I/5rAY5Ss=; b=M6uqJUFvyfdhKV43oqLnfe23K4ft9DjDegZs7HexwY4KqZFzicrCT0ofThmd5NTHv5 j+mubQAVDRj4VpkVvzxkyQNeuunOvay8LFkwzSKnMXsBIhdU3lqO3isyCdEkFbhotVGx EaE9oUsJKtWDPzFfVnVjLAG9ftr1UpDsWn6/TPo2xsxHNXL0MQZPVnINzA1+xcWRQ1Ny AsOYZwVUZNGmIB0QCRT75X+t3/cjzQSbRNl3rKEYApbfmhohsNnr6J9N5Xlr6MNbU/LH PQq48LtpWCU2E+DKdUUnwoTDELPur2U9ItlwHbXt+7wiZ7172wjiUmFvqJAD9P+FWJdO fvmw== 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 f23si2273255oti.283.2020.03.11.23.00.06; Wed, 11 Mar 2020 23:00:19 -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 S2387884AbgCLF7u (ORCPT + 99 others); Thu, 12 Mar 2020 01:59:50 -0400 Received: from shards.monkeyblade.net ([23.128.96.9]:56002 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387810AbgCLF7u (ORCPT ); Thu, 12 Mar 2020 01:59:50 -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 B5D9014CCC99D; Wed, 11 Mar 2020 22:59:49 -0700 (PDT) Date: Wed, 11 Mar 2020 22:59:49 -0700 (PDT) Message-Id: <20200311.225949.740386769094866809.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]); Wed, 11 Mar 2020 22:59:50 -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 I'll apply this to net-next, thank you.