From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <netdev-owner@vger.kernel.org>
Received: from shards.monkeyblade.net ([184.105.139.130]:36168 "EHLO
        shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1750738AbeBUWtq (ORCPT
        <rfc822;netdev@vger.kernel.org>); Wed, 21 Feb 2018 17:49:46 -0500
Date: Wed, 21 Feb 2018 17:49:45 -0500 (EST)
Message-Id: <20180221.174945.1505181795338768522.davem@davemloft.net>
To: sharpd@cumulusnetworks.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 1/1] net: Allow a rule to track originating
 protocol
From: David Miller <davem@davemloft.net>
In-Reply-To: <20180220135558.8469-2-sharpd@cumulusnetworks.com>
References: <20180220135558.8469-2-sharpd@cumulusnetworks.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

From: Donald Sharp <sharpd@cumulusnetworks.com>
Date: Tue, 20 Feb 2018 08:55:58 -0500

> Allow a rule that is being added/deleted/modified or
> dumped to contain the originating protocol's id.
> 
> The protocol is handled just like a routes originating
> protocol is.  This is especially useful because there
> is starting to be a plethora of different user space
> programs adding rules.
> 
> Allow the vrf device to specify that the kernel is the originator
> of the rule created for this device.
> 
> Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>

Looks good, applied, thanks Donald.