[ovs-dev] [PATCH v2 3/3] Implement OFPT_TABLE_STATUS Message.

Saloni Jain saloni.jain at tcs.com
Tue Aug 25 09:51:24 UTC 2015

Hi Ben,

TCS has a team working on the vacancy events feature. 
Rishi is part of that team and have contributed some part of code in this patch.
That is why there name has been added in the signoff chain.

I am reposting version 3 of the patch rebased with latest master for your reference.
Please provide your feedback on the same.

Thanks and Regards,
Saloni Jain
Tata Consultancy Services
Mailto: saloni.jain at tcs.com
Website: http://www.tcs.com
Experience certainty.	IT Services
Business Solutions

-----"dev" <dev-bounces at openvswitch.org> wrote: -----
To: saloni.jain12 at gmail.com
From: Ben Pfaff 
Sent by: "dev" 
Date: 08/22/2015 03:39AM
Cc: dev at openvswitch.org, deepankar.gupta at tcs.com, partha.datta at tcs.com, Rishi Bamba <rishi.bamba at tcs.com>
Subject: Re: [ovs-dev] [PATCH v2 3/3] Implement OFPT_TABLE_STATUS Message.

On Wed, Aug 19, 2015 at 12:54:37PM +0530, saloni.jain12 at gmail.com wrote:
> From: Saloni Jain <saloni.jain at tcs.com>
> On change in a table state, the controller needs to be informed with
> the OFPT_TABLE_STATUS message. The message is sent with reason
> OFPTR_VACANCY_DOWN or OFPTR_VACANCY_UP in case of change in remaining
> space eventually crossing any one of the threshold.
> Signed-off-by: Saloni Jain <saloni.jain at tcs.com>
> Signed-off-by: Rishi Bamba <rishi.bamba at tcs.com>

Presumably you are the author.  Since you are providing the patch, that
means that you should have the final signoff.  Who is Rishi?
dev mailing list
dev at openvswitch.org
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you

More information about the dev mailing list