All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, Hannes Reinecke <hare@suse.de>
Subject: Re: [PATCH] add TIMEOUT to firmware_class hotplug event
Date: Thu, 17 Mar 2005 12:07:55 +0100	[thread overview]
Message-ID: <1111057675.6675.4.camel@localhost.localdomain> (raw)
In-Reply-To: <20050317054602.GA14459@kroah.com>

On Wed, 2005-03-16 at 21:46 -0800, Greg KH wrote:
> On Thu, Mar 17, 2005 at 03:34:31AM +0100, Kay Sievers wrote:
> > On Tue, 2005-03-15 at 09:25 +0100, Hannes Reinecke wrote:
> > > The current implementation of the firmware class breaks a fundamental
> > > assumption in udevd: that the physical device can be initialised fully
> > > prior to executing the next event for that device.
> > 
> > Here we add a TIMEOUT value to the hotplug environment of the firmware
> > requesting event. I will adapt udevd not to wait for anything else, if
> > it finds a TIMEOUT key.
> 
> Can't you just trigger off of the FIRMWARE variable instead?

Sure, that will work too. I just thought it would be nice to give
userspace a hint about the event behavior the kernel expects, instead of
adding an exception to the udevd event management?

Thanks,
Kay


  reply	other threads:[~2005-03-17 12:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-17  2:34 [PATCH] add TIMEOUT to firmware_class hotplug event Kay Sievers
2005-03-17  5:46 ` Greg KH
2005-03-17 11:07   ` Kay Sievers [this message]
2005-03-17 22:55     ` Greg KH
2005-03-17 23:56 ` Greg KH

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=1111057675.6675.4.camel@localhost.localdomain \
    --to=kay.sievers@vrfy.org \
    --cc=greg@kroah.com \
    --cc=hare@suse.de \
    --cc=linux-kernel@vger.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 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.