Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/2] Adding yavta (Yet Another V4L2 Test Application) as a package
Date: Thu, 10 Jan 2013 14:00:38 +0100	[thread overview]
Message-ID: <20130110140038.404c7d92@skate> (raw)
In-Reply-To: <1357822531-8938-1-git-send-email-kpa_info@yahoo.fr>

Dear kpa_info at yahoo.fr,

On Thu, 10 Jan 2013 13:55:30 +0100, kpa_info at yahoo.fr wrote:
> From: Patrick Gerber <kpa_info@yahoo.fr>
> 
> 
> Signed-off-by: Patrick Gerber <kpa_info@yahoo.fr>

For both:

Acked-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Tested-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>

Note that I did only a build test, not a runtime test. But I did the
build test with a minimal toolchains:

 * One test with a uClibc toolchain with just thread support, but no
   rpc, no ipv6, no largefile, no C++, no nothing.

 * On test with a uClibc toolchain without thread support, but with
   rpc, ipv6, largefile, C++, etc.

This should help Peter bring those packages in.

The only nitpick I could do is on the commit title. We normally do:

	yavta: new package
	media-ctl: new package

But I'm really nitpicking here :-)

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      parent reply	other threads:[~2013-01-10 13:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-10 12:55 [Buildroot] [PATCH v3 1/2] Adding yavta (Yet Another V4L2 Test Application) as a package kpa_info at yahoo.fr
2013-01-10 12:55 ` [Buildroot] [PATCH v3 2/2] Adding media-ctl " kpa_info at yahoo.fr
2013-01-10 13:00 ` 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=20130110140038.404c7d92@skate \
    --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