From: Greg KH <greg@kroah.com>
To: "goggin, edward" <egoggin@emc.com>
Cc: "'dm-devel@redhat.com'" <dm-devel@redhat.com>
Subject: Re: patch to bus_add_device to delay call to device_attach till a fter "bus" and bus id sym links are set up
Date: Thu, 10 Nov 2005 22:16:39 -0800 [thread overview]
Message-ID: <20051111061639.GC12008@kroah.com> (raw)
In-Reply-To: <C2EEB4E538D3DC48BF57F391F422779321ADEC@srmanning.eng.emc.com>
On Thu, Nov 10, 2005 at 08:40:43PM -0500, goggin, edward wrote:
> > -----Original Message-----
> > From: Greg KH [mailto:greg@kroah.com]
> > Sent: Thursday, November 10, 2005 5:40 PM
> > To: goggin, edward
> > Cc: 'dm-devel@redhat.com'
> > Subject: Re: patch to bus_add_device to delay call to
> > device_attach till after "bus" and bus id sym links are set up
> >
> > On Thu, Nov 10, 2005 at 03:03:53PM -0500, goggin, edward wrote:
> > > Resend (hopefully) without line wrap.
> >
> > Nope, linewrap still there :(
> >
> > As well as a lack of Signed-off-by: line :(
> >
> > > Patch to drivers/base/bus.c:bus_add_device to delay the
> > driver_attach
> > > call until after the "bus" and bus_id symbolic links for
> > the device exist
> > > so that a hotplug/uevent handler will not fail to find
> > these links already
> > > established for a newly added device.
> >
> > What version of udev are you running that causes you to see this
> > problem?
>
> Using uevents not hotplug events. Uevent handler is in multipathd.
> Udev is not involved.
See my previous comment about how you should make it involved :)
thanks,
greg k-h
prev parent reply other threads:[~2005-11-11 6:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-11 1:40 patch to bus_add_device to delay call to device_attach till a fter "bus" and bus id sym links are set up goggin, edward
2005-11-11 6:16 ` Greg KH [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=20051111061639.GC12008@kroah.com \
--to=greg@kroah.com \
--cc=dm-devel@redhat.com \
--cc=egoggin@emc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.