All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [patch] udevd - allow to bypass sequence number
Date: Thu, 05 Feb 2004 01:37:43 +0000	[thread overview]
Message-ID: <20040205013743.GB6525@kroah.com> (raw)
In-Reply-To: <20040205002709.GA1156@vrfy.org>

On Thu, Feb 05, 2004 at 01:27:09AM +0100, Kay Sievers wrote:
> This patch allows udevsend to be called by the user and not only by the
> kernel with its SEQNUM. If no SEQNUM is given, we move the event straight
> to the exec queue and don't look if something is missing.
> 
> I don't know if this is really needed, but some people seem trying to
> send events trough udevd instead of calling udev directly with their
> scripts and confuse the reorder logic with that.
> 
> So at least, we may remove this source of confusion and udevsend is much
> much faster back than udev itself and it will also block concurrent events
> for the same devpath.

Applied, thanks.

greg k-h


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

      reply	other threads:[~2004-02-05  1:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-05  0:27 [patch] udevd - allow to bypass sequence number Kay Sievers
2004-02-05  1:37 ` 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=20040205013743.GB6525@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-hotplug@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.