On Mon, Jul 28, 2014 at 06:30:29PM +, Yuval Mintz wrote:
> > On Mon, Jul 28, 2014 at 06:52:48PM +0200, Luis R. Rodriguez wrote:
> > > On Mon, Jul 28, 2014 at 03:46:32PM +, Yuval Mintz wrote:
> > > > Sorry for not being clear, but I didn't meant 'what guarantees that the
> > > > device
> >
> On Mon, Jul 28, 2014 at 06:52:48PM +0200, Luis R. Rodriguez wrote:
> > On Mon, Jul 28, 2014 at 03:46:32PM +, Yuval Mintz wrote:
> > > Sorry for not being clear, but I didn't meant 'what guarantees that the
> > > device
> > > will be added to the deferred probe', but rather what guarantees th
On Mon, Jul 28, 2014 at 06:52:48PM +0200, Luis R. Rodriguez wrote:
> On Mon, Jul 28, 2014 at 03:46:32PM +, Yuval Mintz wrote:
> > > Subject: Re: [PATCH 1/3] driver core: enable drivers to use deferred
> > > probe from
> > > init
> > >
> > >
On Mon, Jul 28, 2014 at 03:46:32PM +, Yuval Mintz wrote:
> > Subject: Re: [PATCH 1/3] driver core: enable drivers to use deferred probe
> > from
> > init
> >
> > On Mon, Jul 28, 2014 at 03:12:11PM +, Yuval Mintz wrote:
> > > Perhaps this is a silly
> Subject: Re: [PATCH 1/3] driver core: enable drivers to use deferred probe
> from
> init
>
> On Mon, Jul 28, 2014 at 03:12:11PM +, Yuval Mintz wrote:
> > Perhaps this is a silly question, but what guarantees that the
> > deferred probe list will actually be t
On Mon, Jul 28, 2014 at 03:12:11PM +, Yuval Mintz wrote:
> > +static int __driver_probe_device(struct device_driver *drv, struct
> > +device *dev) {
> > + if (drv->delay_probe && !dev->init_delayed_probe) {
> > + dev_info(dev, "Driver %s requests probe deferral on init\n",
> > +
> +static int __driver_probe_device(struct device_driver *drv, struct
> +device *dev) {
> + if (drv->delay_probe && !dev->init_delayed_probe) {
> + dev_info(dev, "Driver %s requests probe deferral on init\n",
> + drv->name);
> + dev->init_delayed_pro
On Mon, Jul 28, 2014 at 7:51 AM, Takashi Iwai wrote:
>
> This field isn't used anywhere actually in the patch...?
Yeah sorry that is not needed, I avoided that by adding the simple
bool on the struct device, forgot to nuke that. Will spin v2 unless I
hear otherwise.
Luis
--
To unsubscribe from
At Mon, 28 Jul 2014 07:34:25 -0700,
Luis R. Rodriguez wrote:
>
> From: "Luis R. Rodriguez"
>
> Tetsuo bisected and found that commit 786235ee "kthread: make
> kthread_create() killable" modified kthread_create() to bail as
> soon as SIGKILL is received. This is causing some issues with
> some dr
From: "Luis R. Rodriguez"
Tetsuo bisected and found that commit 786235ee "kthread: make
kthread_create() killable" modified kthread_create() to bail as
soon as SIGKILL is received. This is causing some issues with
some drivers and at times boot. Joseph then found that failures
occur as the system
10 matches
Mail list logo
