From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [patch] pass SEQNUM trough udevd
Date: Mon, 06 Sep 2004 09:08:50 +0000 [thread overview]
Message-ID: <1094461730.7587.15.camel@localhost.localdomain> (raw)
In-Reply-To: <20040829202430.GA15492@vrfy.org>
On Sun, 2004-09-05 at 10:08 +0200, Greg KH wrote:
> On Sun, Aug 29, 2004 at 10:24:30PM +0200, Kay Sievers wrote:
> > Hi,
> > here we change udevd to pass the SEQNUM from the hotplug environment
> > to udev and the dev.d/ scripts. We need this for HAL to match the
> > hotplug event with the dev.d/ events.
> >
> > It also changes the type from int to long to match the kernel.
>
> Applied, thanks.
>
> Hm, shouldn't that be unsigned long?
Yes, right, it should. But we currently use a -1 if we want to skip the
udevd reordering, so I didn't change that to unsigned.
With the SEQNUM-in-sysfs patch, the kernel will use u64 and starts with
1 as the first SEQNUM, right?
I will catch up to unsigned long long with the upcoming patch, that will
add the seqnum init with the sysfs value to udevd.
Thank,
Kay
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_idP47&alloc_id\x10808&op=click
_______________________________________________
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
next prev parent reply other threads:[~2004-09-06 9:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-29 20:24 [patch] pass SEQNUM trough udevd Kay Sievers
2004-09-05 8:08 ` Greg KH
2004-09-06 9:08 ` Kay Sievers [this message]
2004-09-09 23:58 ` 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=1094461730.7587.15.camel@localhost.localdomain \
--to=kay.sievers@vrfy.org \
--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.