On 11/8/2017 1:31 AM, Valentin Vidic wrote:
On Wed, Nov 08, 2017 at 04:24:48AM -0500, Sowmini Varadhan wrote:
I just tried setting up a git pull-request for this to Valentin's repo,
I'm not sure if I followed procedures correctly (sending text patches to
a list comes more naturally to me, and I
On Wed, Nov 08, 2017 at 04:24:48AM -0500, Sowmini Varadhan wrote:
> I just tried setting up a git pull-request for this to Valentin's repo,
> I'm not sure if I followed procedures correctly (sending text patches to
> a list comes more naturally to me, and I may have fat-fingered something)
>
> To
On (11/08/17 08:02), Hannes Reinecke wrote:
> We tried to get the list maintainership moved to over to us by the time
> Intel decided to drop FCoE. But for some reasons this never worked out,
> so while the list is technically alive we don't have any means of
> managing it.
> Maybe we should be mov
On 11/07/2017 04:56 PM, Sowmini Varadhan wrote:
>
> We are trying to use DCBX via lldpad for some of our applications,
> and finding/fixing bugs and enhancements as we go.
>
> However our attempts to upstream these fixes is encountering silence
> from the lldp-devel list e.g.,
> http://lists.o
On Tue, Nov 07, 2017 at 10:56:43AM -0500, Sowmini Varadhan wrote:
> We are trying to use DCBX via lldpad for some of our applications,
> and finding/fixing bugs and enhancements as we go.
>
> However our attempts to upstream these fixes is encountering silence
> from the lldp-devel list e.g.,
>
We are trying to use DCBX via lldpad for some of our applications,
and finding/fixing bugs and enhancements as we go.
However our attempts to upstream these fixes is encountering silence
from the lldp-devel list e.g.,
http://lists.open-lldp.org/pipermail/lldp-devel/2017-October/001252.html
An
