ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robherring2@gmail.com>
To: "Luis R. Rodriguez" <mcgrof@kernel.org>
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: Sun, 30 Oct 2016 21:13:34 -0500	[thread overview]
Message-ID: <CAL_JsqJ95-7mE+qW8zzPeEPMsOCTXZc-8m8MG-NogM2=os3zBQ@mail.gmail.com> (raw)
In-Reply-To: <CAB=NE6XscoaYq7_0wbEtgdGZt-duhMb6a-o8O+09FrJRy9EkLQ@mail.gmail.com>

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.

> 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?

Rob

  parent reply	other threads:[~2016-10-31  2:13 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 [this message]
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='CAL_JsqJ95-7mE+qW8zzPeEPMsOCTXZc-8m8MG-NogM2=os3zBQ@mail.gmail.com' \
    --to=robherring2@gmail.com \
    --cc=broonie@sirena.org.uk \
    --cc=jkosina@suse.cz \
    --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