From: Luca Ceresoli via buildroot <buildroot@buildroot.org>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Herve Codina <herve.codina@bootlin.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2] package/linux-tools: add USB tools (testusb and ffs-test)
Date: Wed, 29 Mar 2023 08:43:51 +0200 [thread overview]
Message-ID: <20230329084351.57721a85@booty> (raw)
In-Reply-To: <20230328195659.GC3204460@scaer>
Hi Yann,
On Tue, 28 Mar 2023 21:56:59 +0200
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> Luca, All,
>
> On 2023-03-27 15:59 +0200, Luca Ceresoli spake thusly:
> > Extend the linux-tools package to also build the userspace USB tools, which
> > currently include testusb and ffs-test.
> >
> > These tools are in the kernel tree since a long time, but a Makefile was
> > added only in 5.9 to allow building in the same way as other tools provided
>
> That is not entirely correct.
>
> The Makefile itself has been present since 2.6.39, but indeed only
> gained an install rule for 5.9:
>
> 4f22ce7045c1 2011-02-17 USB: tools: Add a Makefile
> 9ca325ffcac4 2020-08-19 tools: usb: move to tools buildsystem
>
> So I've tweaked the commit log accordingly.
I think the original sentence somehow had the same meaning, even though
it would possibly take a lawyer to prove that... Your rewrite is way
more clear (and fun). Thanks!
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-03-29 6:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 13:59 [Buildroot] [PATCH v2] package/linux-tools: add USB tools (testusb and ffs-test) Luca Ceresoli via buildroot
2023-03-27 14:52 ` Herve Codina via buildroot
2023-03-28 19:56 ` Yann E. MORIN
2023-03-29 6:43 ` Luca Ceresoli via buildroot [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=20230329084351.57721a85@booty \
--to=buildroot@buildroot.org \
--cc=herve.codina@bootlin.com \
--cc=luca.ceresoli@bootlin.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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