From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/linux-tools: add support for Hyper-V tools
Date: Fri, 6 Dec 2019 15:17:12 +0100 [thread overview]
Message-ID: <20191206151712.4a3ea674@windsurf> (raw)
In-Reply-To: <509f4b23-4223-06e4-508d-295d1a598f5a@eu.citrix.com>
Hello,
+Pascal in Cc.
On Fri, 6 Dec 2019 13:33:50 +0000
Simon Rowe <simon.rowe@eu.citrix.com> wrote:
> What's the probability of that, someone else just sent a patch 15
> minutes ago while I was testing this one,
Pascal: the approach of Simon is to have a single option to
build/install all tools. Do we really need one option per tool like you
implemented? In which use cases would only a subset of the tools be
needed? What is the installed size of each tool?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-12-06 14:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 13:31 [Buildroot] [PATCH 1/1] package/linux-tools: add support for Hyper-V tools Simon Rowe
2019-12-06 13:33 ` Simon Rowe
2019-12-06 14:17 ` Thomas Petazzoni [this message]
2019-12-06 14:20 ` Pascal de Bruijn
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=20191206151712.4a3ea674@windsurf \
--to=thomas.petazzoni@bootlin.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