mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: horatiu.vultur@microchip.com
Cc: nikolay@cumulusnetworks.com, roopa@cumulusnetworks.com,
	kuba@kernel.org, jiri@mellanox.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, bridge@lists.linux-foundation.org,
	UNGLinuxDriver@microchip.com
Subject: Re: [PATCH net-next v3 0/3] bridge: mrp: Add support for getting the status
Date: Thu, 02 Jul 2020 14:19:31 -0700 (PDT)	[thread overview]
Message-ID: <20200702.141931.1713593201879768648.davem@davemloft.net> (raw)
In-Reply-To: <20200702081307.933471-1-horatiu.vultur@microchip.com>

From: Horatiu Vultur <horatiu.vultur@microchip.com>
Date: Thu, 2 Jul 2020 10:13:04 +0200

> This patch series extends the MRP netlink interface to allow the userspace
> daemon to get the status of the MRP instances in the kernel.
> 
> v3:
>   - remove misleading comment
>   - fix to use correctly the RCU
> 
> v2:
>   - fix sparse warnings

Series applied, thank you.

      parent reply	other threads:[~2020-07-02 21:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-02  8:13 Horatiu Vultur
2020-07-02  8:13 ` [PATCH net-next v3 1/3] bridge: uapi: mrp: Extend MRP attributes to get " Horatiu Vultur
2020-07-02 10:01   ` Nikolay Aleksandrov
2020-07-02  8:13 ` [PATCH net-next v3 2/3] bridge: mrp: Add br_mrp_fill_info Horatiu Vultur
2020-07-02 10:01   ` Nikolay Aleksandrov
2020-07-02  8:13 ` [PATCH net-next v3 3/3] bridge: Extend br_fill_ifinfo to return MPR status Horatiu Vultur
2020-07-02 10:05   ` Nikolay Aleksandrov
2020-07-02 21:19 ` David Miller [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=20200702.141931.1713593201879768648.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=bridge@lists.linux-foundation.org \
    --cc=horatiu.vultur@microchip.com \
    --cc=jiri@mellanox.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nikolay@cumulusnetworks.com \
    --cc=roopa@cumulusnetworks.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®