From: Theodore Ts'o <tytso@mit.edu>
To: Rob Herring <robherring2@gmail.com>
Cc: Jiri Kosina <jkosina@suse.cz>, Mark Brown <broonie@sirena.org.uk>,
"ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] Schedule slot suggestion- Generic drivers - core topic
Date: Mon, 31 Oct 2016 00:47:09 -0400 [thread overview]
Message-ID: <20161031044708.wpfzazdj65ibtqgj@thunk.org> (raw)
In-Reply-To: <CAL_JsqJ95-7mE+qW8zzPeEPMsOCTXZc-8m8MG-NogM2=os3zBQ@mail.gmail.com>
On Sun, Oct 30, 2016 at 09:13:34PM -0500, Rob Herring wrote:
> On Fri, Oct 28, 2016 at 4:16 PM, Luis R. Rodriguez <mcgrof@kernel.org> wrote:
> > I see some open slots for Monday, there is some overlap in interest
> > between the Audio workshop folks and the tech topic for Tuesday
> > "addressing complex dependencies". We seem to have come to some
> > arrangement to split topics up to avoid such overlap, but one subject
> > overlapping both, but that seems more appropriate for the core day is
> > "Generic drivers":
> >
> > 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.
>
> This is a looming, unsolved problem for DT as well. We can potentially
> bind different drivers to same device if the device has multiple
> compatible strings. There's not any control of which one binds first
> either other than link or initcall order.
So in general, sessions, either at the Kernel Summit, or the LPC,
which are of the form, "we should bell the cat", generally aren't
particularly productive.
>From what I can tell, people have hacks that mostly work, but they
take the form of hard-coded lists or quirk tables, and fact that they
are hacks are making people sad. Is that a fair summary?
If people have ideas towards a better solution, or better yet, a
patch, and there is resistance to accepting the patch, or if there are
multiple competing solutions, then it's much more likely we would make
forward progress by scheduling a sessions.
Do we have something that makes it likely that we would make forwawrd
progress by scheduling such a session on Monday
> > It might be good then to move this to a Monday slot, provided most
> > interested folks can and will be there. Thoughts?
>
> I'd like to be there and won't be there on Mon.
>
> BTW, is there a schedule for Tues published?
There is are the Audio, RDMA, and Wireless workshops. We also
currently have an "Addressing Complex Depndencies" session scheduled
for Tuesday at 9:30am.
Please see:
https://www.linuxplumbersconf.org/2016/ocw/events/LPC2016/schedule
and
http://goo.gl/qtSi1v
Cheers,
- Ted
prev parent reply other threads:[~2016-10-31 4:47 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
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 [this message]
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=20161031044708.wpfzazdj65ibtqgj@thunk.org \
--to=tytso@mit.edu \
--cc=broonie@sirena.org.uk \
--cc=jkosina@suse.cz \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=robherring2@gmail.com \
/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