From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: Greg KH <greg@kroah.com>
Cc: Jiri Kosina <jkosina@suse.cz>, 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 14:25:05 -0700 [thread overview]
Message-ID: <CAB=NE6XzjMJKkJ8Fyocs-9HNpsouH0M2immu9e7uUfp55a6bHw@mail.gmail.com> (raw)
In-Reply-To: <20161028212310.GA25668@kroah.com>
On Fri, Oct 28, 2016 at 2:23 PM, Greg KH <greg@kroah.com> wrote:
> On Fri, Oct 28, 2016 at 02:16:59PM -0700, 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.
>
> We have hacks for this today? What do you mean by this, quirks?
The thread in question was rather huge, this was just *one* of the
topics that came up, and I was not the one who brought it up.
> People have been talking about this since the 2.4 days, but I have yet
> to see any code for it. I'd love to see something be proposed, with
> code, but note, you need to be aware of why it's been only talked about
> for that long without any code being written :)
Ah I see..
> Why can't this be done in email?
Perhaps, and if so then saves us time.
Luis
next prev parent reply other threads:[~2016-10-28 21:25 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
2016-10-28 21:23 ` Greg KH
2016-10-28 21:25 ` Luis R. Rodriguez [this message]
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='CAB=NE6XzjMJKkJ8Fyocs-9HNpsouH0M2immu9e7uUfp55a6bHw@mail.gmail.com' \
--to=mcgrof@kernel.org \
--cc=broonie@sirena.org.uk \
--cc=greg@kroah.com \
--cc=jkosina@suse.cz \
--cc=ksummit-discuss@lists.linuxfoundation.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