netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Sergey Ryazanov <ryazanov.s.a@gmail.com>,
	Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org, Loic Poulain <loic.poulain@linaro.org>
Subject: Re: [PATCH iproute2-next v2 0/2] ip: wwan links management support
Date: Fri, 25 Jun 2021 22:41:34 -0600	[thread overview]
Message-ID: <fb8f9f7a-a4de-e2f0-1e4c-c1976907df65@gmail.com> (raw)
In-Reply-To: <20210622235256.25499-1-ryazanov.s.a@gmail.com>

On 6/22/21 5:52 PM, Sergey Ryazanov wrote:
> This short series introduces support for WWAN links  support.
> 
> First patch adds support for new common attributes: parent device name
> and parent device bus name. The former attribute required to create a
> new WWAN link. Finally, the second patch introduces support for a new
> 'wwan' link type.
> 
> Changelong:
>   v1 -> v2
>     * shorten the 'parentdevbus' parameter to 'parentbus', as Parav
>       suggested and Loic recalled
>   RFC -> v1
>     * drop the kernel headers update patch
>     * add a parent device bus attribute support
>     * shorten the 'parentdev-name' parameter to just 'parentdev'
> 
> Sergey Ryazanov (2):
>   iplink: add support for parent device
>   iplink: support for WWAN devices
> 
>  ip/Makefile      |  2 +-
>  ip/ipaddress.c   | 14 ++++++++++
>  ip/iplink.c      |  9 ++++--
>  ip/iplink_wwan.c | 72 ++++++++++++++++++++++++++++++++++++++++++++++++
>  4 files changed, 94 insertions(+), 3 deletions(-)
>  create mode 100644 ip/iplink_wwan.c
> 

applied to iproute2-next. Thanks,

      parent reply	other threads:[~2021-06-26  4:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-22 23:52 [PATCH iproute2-next v2 0/2] ip: wwan links management support Sergey Ryazanov
2021-06-22 23:52 ` [PATCH iproute2-next v2 1/2] iplink: add support for parent device Sergey Ryazanov
2021-06-22 23:52 ` [PATCH iproute2-next v2 2/2] iplink: support for WWAN devices Sergey Ryazanov
2021-06-26  4:41 ` David Ahern [this message]

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=fb8f9f7a-a4de-e2f0-1e4c-c1976907df65@gmail.com \
    --to=dsahern@gmail.com \
    --cc=loic.poulain@linaro.org \
    --cc=netdev@vger.kernel.org \
    --cc=ryazanov.s.a@gmail.com \
    --cc=stephen@networkplumber.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).