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]:32874 "EHLO
        shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1752729AbeBSQYP (ORCPT
        <rfc822;netdev@vger.kernel.org>); Mon, 19 Feb 2018 11:24:15 -0500
Date: Mon, 19 Feb 2018 11:24:14 -0500 (EST)
Message-Id: <20180219.112414.1368003412958614845.davem@davemloft.net>
To: sharpd@cumulusnetworks.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 0/2] Allow rules to track originating protocol
From: David Miller <davem@davemloft.net>
In-Reply-To: <20180217123148.26733-1-sharpd@cumulusnetworks.com>
References: <20180217123148.26733-1-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: Sat, 17 Feb 2018 07:31:46 -0500

> Add the ability for the kernel to track the originating protocol
> for when new rules are added to the kernel.

I think you need to collapse these two patches together.

The first patch will create a situation where VRF rules cannot be
deleted properly since the protocol field is not being initialized,
and that would be a regression.

Thank you.