From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] lldpd: new package
Date: Wed, 20 Jan 2016 23:03:27 +0100 [thread overview]
Message-ID: <20160120230327.058a99c4@free-electrons.com> (raw)
In-Reply-To: <1453201853-31045-1-git-send-email-julien.floret@6wind.com>
Dear Julien Floret,
On Tue, 19 Jan 2016 12:10:53 +0100, Julien Floret wrote:
> lldpd is a 802.1ab implementation (LLDP) to help you locate neighbors
> of all your equipments.
>
> LLDP is an industry standard protocol designed to supplant
> proprietary Link-Layer protocols such as EDP or CDP. The goal of LLDP
> is to provide an inter-vendor compatible mechanism to deliver
> Link-Layer notifications to adjacent network devices.
>
> https://vincentbernat.github.io/lldpd/
>
> Signed-off-by: Julien Floret <julien.floret@6wind.com>
> ---
> Changes v1 -> v2:
> - rename BR2_PACKAGE_LLDPD_CUSTOM to BR2_PACKAGE_LLDPD_CUSTOM_TLV
> - explicitely disable privsep, xml, snmp, json, seccomp
> - remove LLDPD_SOURCE (same as default value)
> - add LLDPD_LICENSE_FILES
> - remove localstatedir configure option (same as default value)
> - use preferred configure option format (with/without, enable/disable)
> - simplify conditionals for configure options
I've applied, with some minor additional changes:
[Thomas:
- add depends on BR2_USE_MMU, since fork() is used
- rewrap Config.in help text]
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-01-20 22:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 10:14 [Buildroot] [PATCH] lldpd: new package Julien Floret
2016-01-18 15:04 ` Thomas Petazzoni
2016-01-18 17:23 ` Julien Floret
2016-01-18 20:13 ` Thomas Petazzoni
2016-01-19 11:10 ` [Buildroot] [PATCH v2] " Julien Floret
2016-01-20 22:03 ` Thomas Petazzoni [this message]
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=20160120230327.058a99c4@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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