From: Jiri Kosina <jikos@kernel.org>
To: "Luis R. Rodriguez" <mcgrof@kernel.org>
Cc: Mark Brown <broonie@sirena.org.uk>,
ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] Schedule slot suggestion- Generic drivers - core topic
Date: Fri, 28 Oct 2016 23:21:33 +0200 (CEST) [thread overview]
Message-ID: <alpine.LNX.2.00.1610282319390.31629@cbobk.fhfr.pm> (raw)
In-Reply-To: <CAB=NE6XscoaYq7_0wbEtgdGZt-duhMb6a-o8O+09FrJRy9EkLQ@mail.gmail.com>
On Fri, 28 Oct 2016, Luis R. Rodriguez wrote:
> Having some generic device driver load, prior to a specific driver, and
> issues / maintenance issues that come with the hacks currently in place
> to support this / re-invent the wheel to support this per subsystem.
>
> It might be good then to move this to a Monday slot, provided most
> interested folks can and will be there. Thoughts?
As this is exactly the (current worked around in not a very nice way)
problem of HID subsystem (hid-generic handling most of the devices "more
or less fine", and then having drivers implementing "specific
functionality on top"), I'd be very much interested in any discussion /
ideas around this topic. I'll be there on monday.
Thanks,
--
Jiri Kosina
SUSE Labs
next prev parent reply other threads:[~2016-10-28 21:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 21:16 Luis R. Rodriguez
2016-10-28 21:21 ` Jiri Kosina [this message]
2016-10-28 21:23 ` Greg KH
2016-10-28 21:25 ` Luis R. Rodriguez
2016-10-28 21:29 ` Jiri Kosina
2016-10-28 21:38 ` Dmitry Torokhov
2016-10-28 21:44 ` Greg KH
2016-10-28 21:51 ` Dmitry Torokhov
2016-10-29 1:12 ` Laurent Pinchart
2016-10-28 21:43 ` Greg KH
2016-10-31 2:13 ` Rob Herring
2016-10-31 4:33 ` Laurent Pinchart
2016-10-31 4:47 ` Theodore Ts'o
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=alpine.LNX.2.00.1610282319390.31629@cbobk.fhfr.pm \
--to=jikos@kernel.org \
--cc=broonie@sirena.org.uk \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=mcgrof@kernel.org \
/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