Received: by 2002:a25:e7d8:0:0:0:0:0 with SMTP id e207csp221804ybh; Fri, 13 Mar 2020 20:44:33 -0700 (PDT) X-Google-Smtp-Source: ADFU+vvIqfxUzkKmORbfL/9MV5BRZssh9HlQOnOSqfQA4T0JfZLPoA4N42Nct0kl/3PP/HSnfHSr X-Received: by 2002:a05:6808:9bb:: with SMTP id e27mr4279771oig.36.1584157473062; Fri, 13 Mar 2020 20:44:33 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1584157473; cv=none; d=google.com; s=arc-20160816; b=GrgZUAKytgtHywmv8aFoGSSzw4faACQzpTPO3h+11J1wtFHzfb7BWzJy6mp6dExwu6 CKEbnDshutdZFhDo+iB45TUt2OA2iCTYMlh+LT9Yyw2aPxeHPrDA6gqrfbRuBf9AuE67 8rjmtmjWoCRGhw9W7vmAAL5WyARfCauYqrvjOjyzka0bhmQ1+1yMbFyazC38tNhego9p 4/kfc2O3/3uHmzfZOencP8wubElOEft4Ruy9AbpHjVcVuuuzqUC4wYQctko2CNCsD6Yp CBGZC7XDI7UjNRr5DS1CyHBUSpznUbBhJ5qMLMWmrPzJNh6NnDnPY42TSC12ShpbjP6x B3gA== 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=AXy17NT/RyOFsiuO3Aj6PaXoY+dTwQ/s/ZFs9RPEqsg=; b=dAAQOcKuVo6BcQln+sW9a8ySVTwzXJBd3eHdlSR1DSQTNaND3c5CN0FIrvedM3S4ml GOqT/0BtOs+CFad2da49Lg53gYZWqA5ZJLztw9uK+7iFwO/W7YXu8siHeyiZ+5eTD8zP tnSWuWwWVtPsRusMuPZbK2Sn52pvl6WVsWKhvyxUvpt/4bsdtwo6+RpshtOyWCVXVfCT rNuL9e0Fq+1GdPMjTa2ZwlRFZMSDxW2pCGx/Cbp1MwITU1hM9q0HGUAYYlugK8GQCztX UyzvdlNKA21XTdlevbE8WnvPVDr1v38umpZmT+BqBhkVcYld7ED2hSaJV34Pjqdvp5Am e5Xg== 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 t6si4502250otc.27.2020.03.13.20.44.18; Fri, 13 Mar 2020 20:44:33 -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 S1726623AbgCNDn6 (ORCPT + 99 others); Fri, 13 Mar 2020 23:43:58 -0400 Received: from shards.monkeyblade.net ([23.128.96.9]:48504 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726399AbgCNDn6 (ORCPT ); Fri, 13 Mar 2020 23:43:58 -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 7E99E15A1577C; Fri, 13 Mar 2020 20:43:57 -0700 (PDT) Date: Fri, 13 Mar 2020 20:43:54 -0700 (PDT) Message-Id: <20200313.204354.1099710416713347967.davem@davemloft.net> To: bay@hackerdom.ru Cc: oliver@neukum.org, gregkh@linuxfoundation.org, info@metux.net, tglx@linutronix.de, kstewart@linuxfoundation.org, linux-usb@vger.kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/2] cdc_ncm: Implement the 32-bit version of NCM Transfer Block From: David Miller In-Reply-To: <20200313213823.178435-1-bay@hackerdom.ru> References: <20200313213823.178435-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]); Fri, 13 Mar 2020 20:43:57 -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: Sat, 14 Mar 2020 02:38:20 +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 This patch is already in my net-next tree. You need to submit the follow-up fix all by itself, relative to my net-next GIT tree. You must always post patches against the GIT tree that your change is targetting, that way you will avoid situations like this. Thank you.