linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Murali Karicheri <m-karicheri2@ti.com>
To: David Miller <davem@davemloft.net>
Cc: <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>
Subject: Re: [net-next v5 PATCH 0/7] Add PRP driver
Date: Thu, 30 Jul 2020 09:41:26 -0400	[thread overview]
Message-ID: <fb10c323-d5c2-93d6-9784-51ff632fb3ff@ti.com> (raw)
In-Reply-To: <20200727.122120.336438917999066726.davem@davemloft.net>

Hi Dave,

On 7/27/20 3:21 PM, David Miller wrote:
> From: Murali Karicheri <m-karicheri2@ti.com>
> Date: Wed, 22 Jul 2020 10:40:15 -0400
> 
>> This series is dependent on the following patches sent out to
>> netdev list. All (1-3) are already merged to net/master as of
>> sending this, but not on the net-next master branch. So need
>> to apply them to net-next before applying this series. v3 of
>> the iproute2 patches can be merged to work with this series
>> as there are no updates since then.
>>
>> [1] https://marc.info/?l=linux-netdev&m=159526378131542&w=2
>> [2] https://marc.info/?l=linux-netdev&m=159499772225350&w=2
>> [3] https://marc.info/?l=linux-netdev&m=159499772425352&w=2
>>
>> This series adds support for Parallel Redundancy Protocol (PRP)
>> in the Linux HSR driver as defined in IEC-62439-3. PRP Uses a
>> Redundancy Control Trailer (RCT) the format of which is
>> similar to HSR Tag. This is used for implementing redundancy.
>   ...
> 
> Series applied to net-next, thank you.
> 
Thanks for applying this series. Just wondering who will
pick up the v3 of the iproute2 patch I have posted to go
with this.

https://marc.info/?l=linux-netdev&m=159499933326135&w=2

I will reply to that thread as well.

Thanks
-- 
Murali Karicheri
Texas Instruments

  reply	other threads:[~2020-07-30 13:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-22 14:40 [net-next v5 PATCH 0/7] Add PRP driver Murali Karicheri
2020-07-22 14:40 ` [net-next v5 PATCH 1/7] hsr: enhance netlink socket interface to support PRP Murali Karicheri
2020-07-22 14:40 ` [net-next v5 PATCH 2/7] net: hsr: introduce common code for skb initialization Murali Karicheri
2020-07-22 14:40 ` [net-next v5 PATCH 3/7] net: hsr: introduce protocol specific function pointers Murali Karicheri
2020-07-22 14:40 ` [net-next v5 PATCH 4/7] net: prp: add supervision frame generation utility function Murali Karicheri
2020-07-22 14:40 ` [net-next v5 PATCH 5/7] net: hsr: define and use proto_ops ptrs to handle hsr specific frames Murali Karicheri
2020-07-22 14:40 ` [net-next v5 PATCH 6/7] net: prp: add packet handling support Murali Karicheri
2020-07-22 14:40 ` [net-next v5 PATCH 7/7] net: prp: enhance debugfs to display PRP info Murali Karicheri
2020-07-24 12:27 ` [net-next v5 PATCH 0/7] Add PRP driver Murali Karicheri
2020-07-24 22:21   ` David Miller
2020-07-27 11:22     ` Murali Karicheri
2020-07-27 19:21 ` David Miller
2020-07-30 13:41   ` Murali Karicheri [this message]
2020-08-04 19:03     ` Murali Karicheri

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=fb10c323-d5c2-93d6-9784-51ff632fb3ff@ti.com \
    --to=m-karicheri2@ti.com \
    --cc=davem@davemloft.net \
    --cc=grygorii.strashko@ti.com \
    --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=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).