From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH meta-oe 1/9] bridge-utils: add
Date: Fri, 16 Dec 2011 08:45:59 +0100 [thread overview]
Message-ID: <jcesvl$4n1$1@dough.gmane.org> (raw)
In-Reply-To: <1324003173-13994-1-git-send-email-b19537@freescale.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 16-12-11 03:39, b19537@freescale.com schreef:
> From: Zhenhua Luo <b19537@freescale.com>
>
> bridge-utils provides tools for ethernet bridging.
>
> Signed-off-by: Zhenhua Luo <b19537@freescale.com> ---
> .../bridge-utils/bridge-utils.inc | 30 +++
> .../bridge-utils/bridge-utils_1.4.bb | 6 +
> .../bridge-utils/files/ifupdown.sh | 245
> ++++++++++++++++++++ 3 files changed, 281 insertions(+), 0 deletions(-)
> create mode 100644
> meta-oe/recipes-connectivity/bridge-utils/bridge-utils.inc create mode
> 100644 meta-oe/recipes-connectivity/bridge-utils/bridge-utils_1.4.bb
> create mode 100644
> meta-oe/recipes-connectivity/bridge-utils/files/ifupdown.sh
>
> diff --git a/meta-oe/recipes-connectivity/bridge-utils/bridge-utils.inc
> b/meta-oe/recipes-connectivity/bridge-utils/bridge-utils.inc new file
> mode 100644 index 0000000..5ac6c83 --- /dev/null +++
> b/meta-oe/recipes-connectivity/bridge-utils/bridge-utils.inc @@ -0,0
> +1,30 @@ +DESCRIPTION = "Tools for ethernet bridging." +HOMEPAGE =
> "http://bridge.sourceforge.net/" +SECTION = "console/network" +LICENSE =
> "GPL"
That's not a valid license
> +DEPENDS = "sysfsutils" +RRECOMMENDS_${PN} = "kernel-module-bridge"
That needs to move below do_install. Does it also need ifupdown? Patch looks
OK otherwise.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org
iEYEARECAAYFAk7q9zcACgkQMkyGM64RGpFR3QCfes5gKH1Jk36n80JUJGUoa1nO
DWsAn1aWYMXjieT5K+xmiwEdACL6Ln+5
=RPWd
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-12-16 7:53 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-16 2:39 [PATCH meta-oe 1/9] bridge-utils: add b19537
2011-12-16 2:39 ` [PATCH meta-oe 2/9] ietutils: add b19537
2011-12-16 7:48 ` Koen Kooi
2011-12-16 2:39 ` [PATCH meta-oe 3/9] ipsec-tools: add b19537
2011-12-16 7:49 ` Koen Kooi
2011-12-16 2:39 ` [PATCH meta-oe 4/9] libnfnetlink: add b19537
2011-12-16 7:50 ` Koen Kooi
2011-12-16 2:39 ` [PATCH meta-oe 5/9] nerperf: add b19537
2011-12-16 7:51 ` Koen Kooi
2011-12-16 9:19 ` Luo Zhenhua-B19537
2011-12-16 9:22 ` Koen Kooi
2011-12-16 21:54 ` Khem Raj
2011-12-19 9:52 ` Luo Zhenhua-B19537
2011-12-19 19:20 ` Khem Raj
2011-12-19 22:31 ` Flanagan, Elizabeth
2011-12-20 2:31 ` Luo Zhenhua-B19537
2011-12-21 6:26 ` Luo Zhenhua-B19537
2011-12-21 17:37 ` Flanagan, Elizabeth
2011-12-22 2:44 ` Luo Zhenhua-B19537
2011-12-29 18:19 ` Flanagan, Elizabeth
2011-12-16 2:39 ` [PATCH meta-oe 6/9] ptpd: add b19537
2011-12-16 7:52 ` Koen Kooi
2011-12-16 21:57 ` Khem Raj
2011-12-16 2:39 ` [PATCH meta-oe 7/9] strongswan: add b19537
2011-12-16 7:53 ` Koen Kooi
2011-12-16 2:39 ` [PATCH meta-oe 8/9] rng-tools: add b19537
2011-12-16 7:53 ` Koen Kooi
2011-12-16 2:39 ` [PATCH meta-oe 9/9] xfsprogs: add b19537
2011-12-16 7:54 ` Koen Kooi
2011-12-16 7:45 ` Koen Kooi [this message]
2011-12-16 8:48 ` [PATCH meta-oe 1/9] bridge-utils: add Luo Zhenhua-B19537
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='jcesvl$4n1$1@dough.gmane.org' \
--to=koen@dominion.thruhere.net \
--cc=openembedded-devel@lists.openembedded.org \
/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