From: Greg KH <gregkh@linuxfoundation.org>
To: Rajat Khandelwal <rajat.khandelwal@linux.intel.com>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-usb@vger.kernel.org, "Khandelwal,
Rajat" <rajat.khandelwal@intel.com>
Subject: Re: ANNOUNCE: thunderbolt-utils-v0.1-rc1
Date: Tue, 18 Jul 2023 19:54:49 +0200 [thread overview]
Message-ID: <2023071834-audibly-proton-6a3a@gregkh> (raw)
In-Reply-To: <2dab15ba-efd0-97cb-dfde-fa6f9d05f5fb@linux.intel.com>
On Tue, Jul 18, 2023 at 10:02:57PM +0530, Rajat Khandelwal wrote:
> Hi,
>
> This is an official announcement that 'thunderbolt-utils', a collection of
> user-space utilities for the TBT/USB4 subsystem is now made public for its first
> release candidate.
>
> # What is it?
>
> The utilities comprise 'lstbt', similar in lines with 'lspci' and 'lsusb',
> which polls the TBT/USB4 subsystem's information including enumerated
> retimers.
>
> The secondary component of the utilities is the goal towards providing
> a collection of available wrappers to provide the abstraction of configuring
> the subsystem in user-space. This is made possible via porting the DMA layer
> from kernel-space to user-space for the subsystem in an IOMMU-protected
> environment.
Cool, but it doesn't build as a normal user:
/usr/bin/ld: cannot open output file /usr/bin/lstbt: Permission denied
Why aren't you using autotools to properly be able to integrate into
everyone's build systems?
Also, you are shelling out to bash a lot, and as root, in this program,
are you sure that's ok?
And finally, why not add some of the USB4 stuff to usbutils? Wouldn't
that be a bit more relevant for people who use those tools already?
thanks,
greg k-h
prev parent reply other threads:[~2023-07-18 17:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 16:32 ANNOUNCE: thunderbolt-utils-v0.1-rc1 Rajat Khandelwal
2023-07-18 17:54 ` Greg KH [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=2023071834-audibly-proton-6a3a@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rajat.khandelwal@intel.com \
--cc=rajat.khandelwal@linux.intel.com \
/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