From: Murali Karicheri <m-karicheri2@ti.com>
To: David Ahern <dsahern@gmail.com>, <davem@davemloft.net>,
<kuba@kernel.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-api@vger.kernel.org>,
<nsekhar@ti.com>, <grygorii.strashko@ti.com>,
<vinicius.gomes@intel.com>, <stephen@networkplumber.org>,
<kuznet@ms2.inr.ac.ru>
Subject: Re: [net-next iproute2 PATCH v3 1/2] iplink: hsr: add support for creating PRP device similar to HSR
Date: Thu, 6 Aug 2020 16:19:46 -0400 [thread overview]
Message-ID: <9bc91459-73f1-df6e-176a-b078a7cc309f@ti.com> (raw)
In-Reply-To: <6632128c-1c4b-4538-81a9-48dd752c8ab3@gmail.com>
On 8/6/20 1:12 PM, David Ahern wrote:
> On 8/6/20 10:04 AM, Murali Karicheri wrote:
>> that the maintainers are different than the netdev maintainers. My bad.
>> The PRP driver support in kernel is merged by Dave to net-next and this
>> iproute2 change has to go with it. So please review and apply this if it
>> looks good. The kernel part merged is at
>
> there was a long delay between iproute2 and commit to net-next. You need
> to re-send the iproute2 patches.
>
OK. Will do. Thanks
--
Murali Karicheri
Texas Instruments
prev parent reply other threads:[~2020-08-06 20:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 15:22 [net-next iproute2 PATCH v3 1/2] iplink: hsr: add support for creating PRP device similar to HSR Murali Karicheri
2020-07-17 15:22 ` [net-next iproute2 PATCH v3 2/2] ip: iplink: prp: update man page for new parameter Murali Karicheri
2020-07-30 13:47 ` [net-next iproute2 PATCH v3 1/2] iplink: hsr: add support for creating PRP device similar to HSR Murali Karicheri
2020-08-04 18:59 ` Murali Karicheri
2020-08-06 16:04 ` Murali Karicheri
2020-08-06 17:12 ` David Ahern
2020-08-06 20:19 ` Murali Karicheri [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=9bc91459-73f1-df6e-176a-b078a7cc309f@ti.com \
--to=m-karicheri2@ti.com \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=grygorii.strashko@ti.com \
--cc=kuba@kernel.org \
--cc=kuznet@ms2.inr.ac.ru \
--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;
as well as URLs for NNTP newsgroup(s).