From: Murali Karicheri <m-karicheri2@ti.com>
To: <davem@davemloft.net>, <kuba@kernel.org>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-api@vger.kernel.org>, <nsekhar@ti.com>,
<vinicius.gomes@intel.com>, <stephen@networkplumber.org>
Subject: Re: [PATCH iproute2 v5 0/2] iplink: hsr: add support for creating PRP device
Date: Fri, 21 Aug 2020 17:13:44 -0400 [thread overview]
Message-ID: <64c3e8a9-94b1-b47c-93e7-186d98eb5e10@ti.com> (raw)
In-Reply-To: <44143c5d-ba93-363f-ca74-f9d7833c403f@ti.com>
Stephen,
On 8/19/20 5:21 PM, Murali Karicheri wrote:
> Hi, Stephen,
>
> On 8/17/20 5:17 PM, Murali Karicheri wrote:
>> This series enhances the iproute2 iplink module to add support
>> for creating PRP device similar to HSR. The kernel part of this
>> is already merged to v5.9 master
>>
>> v5 - addressed comment from Stephen Hemminger
>> - Sending this with a iproute2 prefix so that this can
>> be merged to v5.9 iprout2 if possible.
>> v3 of the series is rebased to iproute2-next/master at
>> git://git.kernel.org/pub/scm/network/iproute2/iproute2-next
>> and send as v4.
>>
>> Please apply this if looks good.
>>
>>
>> Murali Karicheri (2):
>> iplink: hsr: add support for creating PRP device similar to HSR
>> ip: iplink: prp: update man page for new parameter
>>
>> ip/iplink_hsr.c | 17 +++++++++++++++--
>> man/man8/ip-link.8.in | 9 ++++++++-
>> 2 files changed, 23 insertions(+), 3 deletions(-)
>>
> Can we merge this version please?
Ping .... Thank you!
--
Murali Karicheri
Texas Instruments
next prev parent reply other threads:[~2020-08-21 21:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 21:17 Murali Karicheri
2020-08-17 21:17 ` [PATCH iproute2 v5 1/2] iplink: hsr: add support for creating PRP device similar to HSR Murali Karicheri
2020-08-17 21:17 ` [PATCH iproute2 v5 2/2] ip: iplink: prp: update man page for new parameter Murali Karicheri
2020-08-19 21:21 ` [PATCH iproute2 v5 0/2] iplink: hsr: add support for creating PRP device Murali Karicheri
2020-08-21 21:13 ` Murali Karicheri [this message]
2020-08-23 4:15 ` Stephen Hemminger
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=64c3e8a9-94b1-b47c-93e7-186d98eb5e10@ti.com \
--to=m-karicheri2@ti.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=stephen@networkplumber.org \
--cc=vinicius.gomes@intel.com \
/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
all inboxes | Powered by JetHome®