From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: linux-hotplug@vger.kernel.org
Subject: udevd.c: tiny bit of dead code
Date: Thu, 21 May 2009 13:53:27 +0000 [thread overview]
Message-ID: <4A155CD7.5000909@tuffmail.co.uk> (raw)
There's an empty if statement here. I don't think it's a bug, it's just
sitting there looking funny :-).
/* lookup event for identical, parent, child device */
static int devpath_busy(struct udev_event *event)
{
struct udev_list_node *loop;
if (event->delaying_seqnum > 0) {
}
/* check if queue contains events we depend on */
udev_list_node_foreach(loop, &event_list) {
next reply other threads:[~2009-05-21 13:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-21 13:53 Alan Jenkins [this message]
2009-05-21 16:32 ` udevd.c: tiny bit of dead code Kay Sievers
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=4A155CD7.5000909@tuffmail.co.uk \
--to=alan-jenkins@tuffmail.co.uk \
--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;
as well as URLs for NNTP newsgroup(s).