From: Oliver Neukum <oneukum@suse.com>
To: Johan Hovold <johan@kernel.org>
Cc: gregkh@linuxfoundation.org, stern@rowland.harvard.edu,
linux-usb@vger.kernel.org
Subject: Can't we have stricter matching for vendor specific devices?
Date: Mon, 20 Jan 2020 13:36:31 +0100 [thread overview]
Message-ID: <1579523791.17973.31.camel@suse.com> (raw)
Hi Johan,
I have looked at your heroic efforts at sanity checking
and I cannot help myself wondering whether this is a winning
strategy. Shall we really specify for each device how many
endpoints it is suposed to have in the probe() method?
Could we extend the matching by a minimum and maximum number
of endpoints and masks for permissible endpoint types?
For class devices this is impossible, but the majority of
drivers are for vendor specific devices.
Regards
Oliver
next reply other threads:[~2020-01-20 12:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 12:36 Oliver Neukum [this message]
2020-01-21 13:24 ` Can't we have stricter matching for vendor specific devices? Johan Hovold
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=1579523791.17973.31.camel@suse.com \
--to=oneukum@suse.com \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=linux-usb@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).