From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] usbip: add a new package
Date: Sat, 10 Dec 2016 14:31:19 +0100 [thread overview]
Message-ID: <20161210143119.778e63b1@free-electrons.com> (raw)
In-Reply-To: <1481272671-6491-1-git-send-email-tal.shorer@gmail.com>
Hello,
On Fri, 9 Dec 2016 10:37:51 +0200, Tal Shorer wrote:
> Add usbip tools (usbip, usbipd) from the running linux source
>
> Signed-off-by: Tal Shorer <tal.shorer@gmail.com>
Thanks for your contribution. However, since usbip tools is provided as
part of the Linux kernel source code, it should be supported by the
package/linux-tools/ package, which already handles similar tools (perf
and others).
However, it is true that the linux-tools infrastructure currently only
handles tools that just need to be built/installed, and not tools that
use autoconf/automake. So most likely, we want to extend
package/linux-tools/linux-tools.mk? Or should we, because usbip is
different, have a separate package?
Cc'ing Yann E. Morin, who did the work on the linux-tools package.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-12-10 13:31 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-09 8:37 [Buildroot] [PATCH] usbip: add a new package Tal Shorer
2016-12-10 13:31 ` Thomas Petazzoni [this message]
2016-12-10 18:39 ` Tal Shorer
2016-12-11 10:06 ` Yann E. MORIN
2016-12-11 13:56 ` Yann E. MORIN
2016-12-11 17:39 ` Tal Shorer
2016-12-11 17:45 ` Yann E. MORIN
2016-12-11 18:12 ` [Buildroot] [PATCH] pkg-generic: run $(PKG)_PRE_RSYNC_HOOKS before checking for the existence of $(SRCDIR) Tal Shorer
2016-12-11 19:19 ` Yann E. MORIN
2016-12-11 19:44 ` [Buildroot] [PATCH] package/usbip: new package Tal Shorer
2016-12-17 15:00 ` [Buildroot] [PATCH] pkg-generic: run $(PKG)_PRE_RSYNC_HOOKS before checking for the existence of $(SRCDIR) Thomas Petazzoni
2016-12-11 18:31 ` [Buildroot] [PATCH] usbip: add a new package Tal Shorer
2016-12-11 19:24 ` Yann E. MORIN
2016-12-11 19:59 ` Arnout Vandecappelle
2016-12-11 21:40 ` Yann E. MORIN
2016-12-11 21:46 ` Tal Shorer
2016-12-11 22:05 ` Yann E. MORIN
2016-12-11 22:11 ` Tal Shorer
2016-12-11 22:20 ` Yann E. MORIN
2016-12-11 22:30 ` Tal Shorer
2016-12-12 9:40 ` Arnout Vandecappelle
2016-12-12 17:25 ` Yann E. MORIN
2016-12-12 22:17 ` Tal Shorer
2016-12-12 22:21 ` [Buildroot] [PATCH v3] usbip: " Tal Shorer
2016-12-13 17:53 ` Yann E. MORIN
2016-12-14 17:28 ` [Buildroot] [PATCH v4] " Tal Shorer
2016-12-21 22:17 ` Tal Shorer
2016-12-22 20:45 ` Yann E. MORIN
2016-12-23 18:24 ` Yann E. MORIN
2016-12-23 19:10 ` Yann E. MORIN
2016-12-13 17:35 ` [Buildroot] [PATCH] usbip: add a " Yann E. MORIN
2016-12-12 17:09 ` [Buildroot] [PATCH v2 1/2] package: linux-tools: allow tools to define configure hooks Tal Shorer
2016-12-12 17:09 ` [Buildroot] [PATCH v2 2/2] package: linux-tools: add usbip Tal Shorer
2016-12-12 17:26 ` Yann E. MORIN
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=20161210143119.778e63b1@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