From: Sebastian Wiesner <lunaryorn@googlemail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: libudev queue finished seqnums
Date: Tue, 10 May 2011 10:59:25 +0000 [thread overview]
Message-ID: <BANLkTimFL5damxWUnD8JqwoOavRhhULbHQ@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=H1sc2tnOYNTY3n8UyJt21mcLxzw@mail.gmail.com>
2011/5/9 Kay Sievers <kay.sievers@vrfy.org>:
> On Sun, May 8, 2011 at 20:32, Sebastian Wiesner
> <lunaryorn@googlemail.com> wrote:
>> I've got a question about libudev, concerning the function
>> "udev_queue_get_seqnum_is_finished()". According to the
>> documentation, it returns a flag, indicating whether the given
>> sequence number has already been processed. In my experiments
>> however, I found this function to always return 1, even for sequence
>> numbers which haven't ocurred yet. The attached test program gives
>> the following output on my system:
>>
>> $ ./udev_queue_sequence_numbers
>> current seqnum: 1662
>> is previous seqnum finished? yes
>> is current seqnum finished? yes
>> is next seqnum finished? yes
>>
>> In my understanding, the last line should have said "no", because the
>> number immediately folllowing the current sequence number has
>> obviously not yet occurred.
>>
>> Am I missing something?
>
> I guess, you need to read the function name as
> _seqnum_is_not_active(). It will return true for all event numbers
> currently not queued, including numbers larger than the currently
> handled one.
Ok, that'd make sense.
Thanks for your help
prev parent reply other threads:[~2011-05-10 10:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-08 18:32 libudev queue finished seqnums Sebastian Wiesner
2011-05-09 9:54 ` Kay Sievers
2011-05-10 10:59 ` Sebastian Wiesner [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=BANLkTimFL5damxWUnD8JqwoOavRhhULbHQ@mail.gmail.com \
--to=lunaryorn@googlemail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox