* question on uapi
@ 2023-07-13 10:39 Oliver Neukum
2023-07-13 13:22 ` Greg KH
0 siblings, 1 reply; 4+ messages in thread
From: Oliver Neukum @ 2023-07-13 10:39 UTC (permalink / raw)
To: USB list
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?
Regards
Oliver
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: question on uapi
2023-07-13 10:39 question on uapi Oliver Neukum
@ 2023-07-13 13:22 ` Greg KH
2023-07-13 13:49 ` Oliver Neukum
0 siblings, 1 reply; 4+ messages in thread
From: Greg KH @ 2023-07-13 13:22 UTC (permalink / raw)
To: Oliver Neukum; +Cc: USB list
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.
greg k-h
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: question on uapi
2023-07-13 13:22 ` Greg KH
@ 2023-07-13 13:49 ` Oliver Neukum
2023-07-13 13:54 ` Greg KH
0 siblings, 1 reply; 4+ messages in thread
From: Oliver Neukum @ 2023-07-13 13:49 UTC (permalink / raw)
To: Greg KH, Oliver Neukum; +Cc: USB list
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.
In this particular case I found that we are lacking definitions
in uapi for authentication descriptors. User space can definitely
see them.
Regards
Oliver
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: question on uapi
2023-07-13 13:49 ` Oliver Neukum
@ 2023-07-13 13:54 ` Greg KH
0 siblings, 0 replies; 4+ messages in thread
From: Greg KH @ 2023-07-13 13:54 UTC (permalink / raw)
To: Oliver Neukum; +Cc: USB list
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
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2023-07-13 13:54 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox