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 1/1] libgphoto2: Add libgphoto2 package
Date: Mon, 10 Apr 2017 13:45:49 +0200	[thread overview]
Message-ID: <20170410134549.6da2679d@free-electrons.com> (raw)
In-Reply-To: <33dd1db4-d5cb-3f49-931d-613dd6967b7d@sensefly.com>

Hello,

Thanks for your new iteration of the libgphoto2 patch!

On Mon, 10 Apr 2017 11:24:32 +0200, Kevin JOLY wrote:

> > Also, can you check this new package with the new test-pkg script ? [3]
> > (17.20.2. How to test your package).  
> I ran the test. Everything was OK except br-arm-cortex-m4-full and 
> br-arm-full-nothread.

What errors did you had with those toolchains? Did you fix those issue
in your v2?

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-04-10 11:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-06  8:33 [Buildroot] [PATCH 1/1] libgphoto2: Add libgphoto2 package Kevin JOLY
2017-04-06 20:36 ` Thomas Petazzoni
2017-04-07  5:14   ` Kevin JOLY
2017-04-07 20:52     ` Romain Naour
2017-04-10  9:24       ` Kevin JOLY
2017-04-10 11:45         ` Thomas Petazzoni [this message]
2017-04-10 12:01           ` Arnout Vandecappelle
2017-04-10 10:20 ` Arnout Vandecappelle
2017-04-10 12:23   ` Kevin JOLY
2017-04-10 13:28     ` Arnout Vandecappelle
  -- strict thread matches above, loose matches on Subject: below --
2017-03-13  7:26 Kevin JOLY
2017-03-08 13:38 Kevin JOLY
2017-03-08 20:10 ` Romain Naour
2017-03-09  6:52   ` Kevin JOLY
2017-03-16 23:17     ` Romain Naour
2017-04-06  8:31       ` Kevin JOLY

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=20170410134549.6da2679d@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