From: Oliver Neukum <oneukum@suse.com>
To: Peter Hutterer <peter.hutterer@who-t.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Bastien Nocera <hadess@hadess.net>,
linux-usb@vger.kernel.org, Alan Stern <stern@rowland.harvard.edu>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>
Subject: Re: [RFC v1] USB: core: add USBDEVFS_REVOKE ioctl
Date: Tue, 26 Apr 2022 09:14:04 +0200 [thread overview]
Message-ID: <7def25c7-0870-accc-c689-4d8eef1b7acf@suse.com> (raw)
In-Reply-To: <YmdYfK5Vi+lEl7FX@quokka>
On 26.04.22 04:27, Peter Hutterer wrote:
>
> chiming in here: the hidraw ioctl is independent (as already mentioned)
> but it's basically the same approach and/or intent. The hidraw revoke ioctl is
> "the evdev revoke, but for hidraw", this one is "the evdev revoke, but for
> usb". Not very creative, but at least we can point to prior art and say "this
> seems to be useful" :)
>
> The primary focus of all this are joystick devices (unless I missed some other
> grand plans Bastien had that I'm not aware of), that should put things in
> context a bit.
>
Hi,
taking the advantages as a given, I must still ask, why this, if it is
so useful,
should be implemented for each subsystem separately. I cannot help but
say that this should go into the VFS.
Regards
Oliver
next prev parent reply other threads:[~2022-04-26 7:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 13:23 [RFC v1] USB: core: add USBDEVFS_REVOKE ioctl Bastien Nocera
2022-04-25 13:28 ` Bastien Nocera
2022-04-25 13:49 ` Oliver Neukum
2022-04-25 14:25 ` Bastien Nocera
2022-04-25 14:45 ` Bastien Nocera
2022-04-25 14:10 ` Greg Kroah-Hartman
2022-04-25 14:28 ` Bastien Nocera
2022-04-25 15:00 ` Greg Kroah-Hartman
2022-04-25 15:17 ` Bastien Nocera
2022-04-25 15:45 ` Greg Kroah-Hartman
2022-04-26 2:27 ` Peter Hutterer
2022-04-26 7:14 ` Oliver Neukum [this message]
2022-04-26 7:21 ` Greg Kroah-Hartman
2022-04-26 8:46 ` Oliver Neukum
2022-04-26 10:07 ` Bastien Nocera
2022-04-26 10:30 ` Greg Kroah-Hartman
2022-04-26 10:37 ` Bastien Nocera
2022-04-26 11:10 ` Greg Kroah-Hartman
2022-04-28 10:28 ` Oliver Neukum
2022-04-28 11:21 ` Bastien Nocera
2022-04-26 10:07 ` Bastien Nocera
2022-04-26 10:07 ` Bastien Nocera
2022-04-25 16:14 ` Alan Stern
2022-04-25 17:09 ` Benjamin Tissoires
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=7def25c7-0870-accc-c689-4d8eef1b7acf@suse.com \
--to=oneukum@suse.com \
--cc=benjamin.tissoires@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=hadess@hadess.net \
--cc=linux-usb@vger.kernel.org \
--cc=peter.hutterer@who-t.net \
--cc=stern@rowland.harvard.edu \
/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