Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] linux-tools: add usbip (USB/IP userspace tools)
Date: Thu, 14 Dec 2017 22:41:49 +0100	[thread overview]
Message-ID: <878te52dia.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20171214095614.5e99e0a0@windsurf.png.is.keysight.com> (Thomas Petazzoni's message of "Thu, 14 Dec 2017 09:56:14 +0100")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

Hi,

 >> sourcery-arm-armv4t [40/47]: SKIPPED
 >> sourcery-arm [41/47]: SKIPPED
 >> sourcery-arm-thumb2 [42/47]: SKIPPED
 >> sourcery-mips64 [43/47]: OK
 >> sourcery-mips [44/47]: OK
 >> sourcery-nios2 [45/47]: OK
 >> sourcery-x86-64 [46/47]: OK
 >> x86_64-ctng_locales-linux-gnu [47/47]: SKIPPED
 >> 47 builds, 19 skipped, 0 build failed, 0 legal-info failed

 > Does it makes sense to include the test-pkg details in the commit log?
 > This is a real open question. We don't do it today, but I might see
 > some value in having it. What do others think ?

I think it does. It is useful information and if it is in the commit
message then it is easy to find back.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2017-12-14 21:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-06 13:29 [Buildroot] [PATCH] linux-tools: add usbip (USB/IP userspace tools) julien.boibessot at free.fr
2017-12-14  8:56 ` Thomas Petazzoni
2017-12-14 21:41   ` Peter Korsgaard [this message]
2017-12-14 21:59   ` Yann E. MORIN
2017-12-22  9:44     ` Julien Boibessot
2018-03-31 14:20       ` Romain Naour

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=878te52dia.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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