From: Joe MacDonald <Joe.MacDonald@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Cc: koen@dominion.thruhere.net
Subject: Re: [PATCH V2][meta-networking] netperf: import from oe-classic and upgrade to 2.6.0
Date: Mon, 19 Nov 2012 11:35:21 -0500 [thread overview]
Message-ID: <20121119163521.GQ5534@windriver.com> (raw)
In-Reply-To: <1352713186-2637-1-git-send-email-Xin.Ouyang@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]
Merged, thanks.
[[oe] [PATCH V2][meta-networking] netperf: import from oe-classic and upgrade to 2.6.0] On 12.11.12 (Mon 17:39) Xin Ouyang wrote:
> V2 Updates:
> * merge two patches into one
> * bb recipe: LICENSE back to "netperf"
> * initscript: add LSB headers
> * initscript: "sed" to replace the hardcodes /usr/sbin to $sbindir.
>
> Xin Ouyang (1):
> netperf: import from oe-classic and upgrade to 2.6.0
>
> .../recipes-support/netperf/files/cpu_set.patch | 30 ++++++++++
> meta-networking/recipes-support/netperf/files/init | 62 ++++++++++++++++++++
> .../recipes-support/netperf/files/vfork.patch | 58 ++++++++++++++++++
> .../recipes-support/netperf/netperf_2.6.0.bb | 57 ++++++++++++++++++
> 4 files changed, 207 insertions(+)
> create mode 100644 meta-networking/recipes-support/netperf/files/cpu_set.patch
> create mode 100644 meta-networking/recipes-support/netperf/files/init
> create mode 100644 meta-networking/recipes-support/netperf/files/vfork.patch
> create mode 100644 meta-networking/recipes-support/netperf/netperf_2.6.0.bb
>
--
-Joe MacDonald.
:wq
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
prev parent reply other threads:[~2012-11-19 16:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 9:39 [PATCH V2][meta-networking] netperf: import from oe-classic and upgrade to 2.6.0 Xin Ouyang
2012-11-12 9:39 ` Xin Ouyang
2012-11-19 16:35 ` Joe MacDonald [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=20121119163521.GQ5534@windriver.com \
--to=joe.macdonald@windriver.com \
--cc=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