All of lore.kernel.org
 help / color / mirror / Atom feed
From: Subash Abhinov Kasiviswanathan <subashab@codeaurora.org>
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, davem@davemloft.net, fengguang.wu@intel.com
Subject: Re: [PATCH net-next 1/1 v2] net: rmnet_data: Initial implementation
Date: Mon, 13 Mar 2017 16:01:15 -0600	[thread overview]
Message-ID: <868aee1b58aa4365708966956decf6d3@codeaurora.org> (raw)
In-Reply-To: <20170313085420.GA1796@nanopsycho>

On 2017-03-13 02:54, Jiri Pirko wrote:
> Mon, Mar 13, 2017 at 08:43:09AM CET, subashab@codeaurora.org wrote:
>> RmNet Data driver provides a transport agnostic MAP (multiplexing and
> 
> Why "data"? Why not just "rmnet"??
> 
> Btw, what is "RmNet". Google does not give me much. Is it some
> priprietady Qualcomm thing? Is there some standard behind it?
> 

Hi Jiri

Rm interface is used to describe an application processor tethered to
Qualcomm Technologies, Inc. modems. Since these are netdevices,
the term RmNet is used. I don't think there are published standards
available for this but I can provide relevant information and
document it as well.

rmnet was used for a USB based physical transport earlier, hence
this platform agnostic multiplexing driver was named as rmnet_data.

  reply	other threads:[~2017-03-13 22:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-13  7:43 [PATCH net-next 0/1 v2] net: Add support for rmnet_data driver Subash Abhinov Kasiviswanathan
2017-03-13  7:43 ` [PATCH net-next 1/1 v2] net: rmnet_data: Initial implementation Subash Abhinov Kasiviswanathan
2017-03-13  8:54   ` Jiri Pirko
2017-03-13 22:01     ` Subash Abhinov Kasiviswanathan [this message]
2017-03-14  6:55       ` Jiri Pirko
2017-03-14 21:19         ` Subash Abhinov Kasiviswanathan
2017-03-13 22:24   ` kbuild test robot
2017-03-24 22:15   ` Dan Williams
2017-03-24 22:21   ` Dan Williams
2017-03-25  0:49     ` Subash Abhinov Kasiviswanathan
2017-03-31 22:41       ` Dan Williams
2017-04-01  5:43         ` Subash Abhinov Kasiviswanathan

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=868aee1b58aa4365708966956decf6d3@codeaurora.org \
    --to=subashab@codeaurora.org \
    --cc=davem@davemloft.net \
    --cc=fengguang.wu@intel.com \
    --cc=jiri@resnulli.us \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.