Re: composite: usb_string_id() doubts

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




--- On Fri, 5/28/10, Michał Nazarewicz <m.nazarewicz@xxxxxxxxxxx> wrote:

> 1. The ID 255 will never be assigned.  Is it intended
> or a bug?

ISTR intentional ... isn't 255 reserved to
indicate "no valid string ID"?  (Either in the
USB spec or in Linux.)  I'd have to check the
spec to verify.


> 2. 'next_string_id' name is not really appropriate since it does not
>     store an ID of a *next* string 

I don't follow.  It's certainly the next
ID returned by that function...

- Dave.


> but *last*
> sting.  It should rather
>     read 'last_string_id', shouldn't it?


--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux