From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: Hannes Reinecke <hare@suse.de>
Cc: netdev@vger.kernel.org, imanti.mendez@oracle.com,
santosh.shilimkar@oracle.com, lldp-devel@open-lldp.org,
Valentin.Vidic@CARNet.hr
Subject: Re: [lldp-devel] Fwd: [PATCH RESEND] Fix segfault on "lldptool -t -i eth2 -V PFC -c enabled"
Date: Wed, 8 Nov 2017 04:24:48 -0500 [thread overview]
Message-ID: <20171108092448.GO4947@oracle.com> (raw)
In-Reply-To: <33ec9840-dc31-6b01-bd8c-0d42254951e1@suse.de>
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 moving it to somewhere else.
I'd support that.. any thoughts on where to move it to?
> But yes, we _do_ take fixes for it.
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!
--Sowmini
next prev parent reply other threads:[~2017-11-08 9:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 15:56 Fwd: [PATCH RESEND] Fix segfault on "lldptool -t -i eth2 -V PFC -c enabled" Sowmini Varadhan
2017-11-07 18:32 ` Valentin Vidic
2017-11-08 7:02 ` [lldp-devel] " Hannes Reinecke
2017-11-08 9:24 ` Sowmini Varadhan [this message]
2017-11-08 9:31 ` Valentin Vidic
2017-11-08 16:44 ` Santosh Shilimkar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171108092448.GO4947@oracle.com \
--to=sowmini.varadhan@oracle.com \
--cc=Valentin.Vidic@CARNet.hr \
--cc=hare@suse.de \
--cc=imanti.mendez@oracle.com \
--cc=lldp-devel@open-lldp.org \
--cc=netdev@vger.kernel.org \
--cc=santosh.shilimkar@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).