From: David Miller <davem@davemloft.net>
To: m-karicheri2@ti.com
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: Fri, 24 Jul 2020 15:21:36 -0700 (PDT) [thread overview]
Message-ID: <20200724.152136.239820662240192829.davem@davemloft.net> (raw)
In-Reply-To: <7133d5ca-e72b-b406-feb2-21429085c96a@ti.com>
From: Murali Karicheri <m-karicheri2@ti.com>
Date: Fri, 24 Jul 2020 08:27:01 -0400
> If there are no more comments, can we consider merging this to
> net-next? I could re-base and repost if there is any conflict.
I can't apply them until I next merge net into net-next, and I don't
know exactly when that will happen yet.
It'd also be nice to get some review and ACK's on this series
meanwhile.
next prev parent reply other threads:[~2020-07-24 22:21 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 [this message]
2020-07-27 11:22 ` Murali Karicheri
2020-07-27 19:21 ` David Miller
2020-07-30 13:41 ` Murali Karicheri
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=20200724.152136.239820662240192829.davem@davemloft.net \
--to=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=m-karicheri2@ti.com \
--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).