netdev - Re: [lldp-devel] Fwd: [PATCH RESEND] Fix segfault on "lldptool -t -i eth2 -V PFC -c enabled"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <4a8c708c-5509-768e-8703-23c020b121db@oracle.com>
Date:   Wed, 8 Nov 2017 08:44:27 -0800
From:   Santosh Shilimkar <santosh.shilimkar@...cle.com>
To:     Valentin Vidic <Valentin.Vidic@...Net.hr>,
        Sowmini Varadhan <sowmini.varadhan@...cle.com>,
        Hannes Reinecke <hare@...e.de>
Cc:     netdev@...r.kernel.org, imanti.mendez@...cle.com,
        lldp-devel@...n-lldp.org, Parav Pandit <parav@...lanox.com>
Subject: Re: [lldp-devel] Fwd: [PATCH RESEND] Fix segfault on "lldptool -t -i
 eth2 -V PFC -c enabled"

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 may have fat-fingered something)
>>
>> To whom should I send this patch?
>>
>> We also have a couple of other patches in the pipeline that we are
>> testing, so setting up a mailing list would be welcomed!
> 
> Right, but my repo is just for Debian packaging :)  We would need a
> SUSE repo or email address where to send patches - I also have few small
> fixes for lldpad and fcoe waiting.
> 
I also heard Mellanox folks have few patches so looping them as well.
IMO email alone will not be enough and a public repo needed so
that latest sources can be available for people developing/using it.

Hannes, you mentioned that you are taking fixes. Is your repo public
where you are applying this fixes. Sorry if I missed that part.

Regards,
Santosh