Linux USB
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Oliver Neukum <oneukum@suse.com>
Cc: USB list <linux-usb@vger.kernel.org>
Subject: Re: question on uapi
Date: Thu, 13 Jul 2023 15:54:27 +0200	[thread overview]
Message-ID: <2023071302-earthlike-groin-da0a@gregkh> (raw)
In-Reply-To: <50eeac98-f790-4532-d067-b9da6e925e30@suse.com>

On Thu, Jul 13, 2023 at 03:49:32PM +0200, Oliver Neukum wrote:
> 
> 
> On 13.07.23 15:22, Greg KH wrote:
> > On Thu, Jul 13, 2023 at 12:39:09PM +0200, Oliver Neukum wrote:
> > > Hi,
> > > 
> > > what is the policy on uapi. It being for user space means
> > > that it should be as complete as possible, even if the kernel does not need stuff,
> > > should it not?
> > 
> > If the kernel does not need it, why add it to a uapi .h file as there is
> > nothing that userspace could do with it, right?
> > 
> > Or are you talking about USB protocols/structures that userspace can use
> > by talking to a USB device directly?
> > 
> > Specifics would be great to have, thanks.
> 
> Hi,
> 
> I wanted to get this clarified in principle.

There's no principle, only specifics :)

> In this particular case I found that we are lacking definitions
> in uapi for authentication descriptors. User space can definitely
> see them.

Then we should add them where needed.

thanks,

greg k-h

      reply	other threads:[~2023-07-13 13:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-13 10:39 question on uapi Oliver Neukum
2023-07-13 13:22 ` Greg KH
2023-07-13 13:49   ` Oliver Neukum
2023-07-13 13: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=2023071302-earthlike-groin-da0a@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=oneukum@suse.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