From: Enrico Mioso <mrkiko.rs@gmail.com>
To: netdev@vger.kernel.org, linux-usb@vger.kernel.org
Cc: Alexey Orishko <alexey.orishko@gmail.com>,
David Laight <David.Laight@aculab.com>
Subject: Re: [PATCH net-next 01/11] net: cdc_ncm: split out rx_max/tx_max update of setup
Date: Tue, 13 May 2014 11:40:36 +0200 (CEST) [thread overview]
Message-ID: <alpine.LNX.2.03.1405131138210.1290@gmail.com> (raw)
Note: I am re-sending the mail, since I sent it privately to Bj*rn only, by
mistake. Sorry. And sorry also for continously mistyping your name: I would
like to learn writing it right! :)
I would also propose some polite warning message regarding what's happening.
Ok, I know it may simply be SPAM for users, but it may help identifying devices
not behaving properly in regard to specifications.
I know - it doesn't make much sense, even considering there are simply devices
that will act like NCM but use AT for signaling reasons. But with this message,
the kernle may inform users about a situation like:
2oh - I am trying to do my best. If performances are not as good as they might
be, proceed with ..."
This is only a proposal, nothing more.
Enrico
next reply other threads:[~2014-05-13 9:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 9:40 Enrico Mioso [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-05-10 15:41 [PATCH net-next 00/11] cdc_ncm: add buffer tuning and stats using ethtool Bjørn Mork
[not found] ` <1399736509-1159-1-git-send-email-bjorn-yOkvZcmFvRU@public.gmane.org>
2014-05-10 15:41 ` [PATCH net-next 01/11] net: cdc_ncm: split out rx_max/tx_max update of setup Bjørn Mork
2014-05-13 8:09 ` Oliver Neukum
2014-05-13 8:49 ` Bjørn Mork
2014-05-13 9:09 ` Oliver Neukum
[not found] ` <1399972165.8278.11.camel-B2T3B9s34ElbnMAlSieJcQ@public.gmane.org>
2014-05-13 9:25 ` Bjørn Mork
2014-05-13 11:07 ` Oliver Neukum
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=alpine.LNX.2.03.1405131138210.1290@gmail.com \
--to=mrkiko.rs@gmail.com \
--cc=David.Laight@aculab.com \
--cc=alexey.orishko@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).