From: David Miller <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
Date: Fri, 13 Mar 2020 20:43:54 -0700 (PDT) [thread overview]
Message-ID: <20200313.204354.1099710416713347967.davem@davemloft.net> (raw)
In-Reply-To: <20200313213823.178435-1-bay@hackerdom.ru>
From: Alexander Bersenev <bay@hackerdom.ru>
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 <bay@hackerdom.ru>
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.
next prev parent reply other threads:[~2020-03-14 3:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-13 21:38 [PATCH 1/2] cdc_ncm: Implement the 32-bit version of NCM Transfer Block Alexander Bersenev
2020-03-13 21:38 ` [PATCH 2/2] cdc_ncm: Fix the build warning Alexander Bersenev
2020-03-14 2:26 ` Jakub Kicinski
2020-03-14 3:43 ` David Miller [this message]
2020-03-14 5:36 ` [PATCH 1/2] cdc_ncm: Implement the 32-bit version of NCM Transfer Block Александр Берсенев
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200313.204354.1099710416713347967.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bay@hackerdom.ru \
--cc=gregkh@linuxfoundation.org \
--cc=info@metux.net \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oliver@neukum.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).