From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: finally solve the bad sysfs-timing for all of us
Date: Wed, 06 Oct 2004 00:21:17 +0000 [thread overview]
Message-ID: <20041006002117.GA8387@vrfy.org> (raw)
In-Reply-To: <20040921171734.GA7778@vrfy.org>
[-- Attachment #1: Type: text/plain, Size: 526 bytes --]
On Tue, Oct 05, 2004 at 01:51:02PM -0700, Greg KH wrote:
> On Tue, Sep 21, 2004 at 10:04:57PM +0200, Kay Sievers wrote:
> > >
> > > For now, it logs the result of the waiting to syslog, to catch any
> > > device, that needs special treatment.
>
> Applied, thanks.
Sorry, I left my debug code in. We don't need to log a successful operation.
On failure we log and ask to report the device, so we hopefully collect all
unusual device representations over the time and can put in in the built-in
exception lists.
Thanks,
Kay
[-- Attachment #2: udev-wait_for_sysfs-debug-01.patch --]
[-- Type: text/plain, Size: 805 bytes --]
===== wait_for_sysfs.c 1.1 vs edited =====
--- 1.1/wait_for_sysfs.c 2004-09-21 22:00:29 +02:00
+++ edited/wait_for_sysfs.c 2004-10-06 02:16:27 +02:00
@@ -206,6 +206,8 @@ int main(int argc, char *argv[], char *e
int loop;
int rc = 0;
+ init_logging("wait_for_sysfs");
+
if (argc != 2) {
dbg("error: subsystem");
return 1;
@@ -326,9 +328,11 @@ int main(int argc, char *argv[], char *e
exit:
if (rc == 0)
- info("result: waiting for sysfs successful '%s'", devpath);
+ dbg("result: waiting for sysfs successful '%s'", devpath);
else
- info("result: waiting for sysfs failed '%s'", devpath);
+ info("error: wait_for_sysfs needs an update to handle the device '%s' "
+ "properly, please report to <linux-hotplug-devel@lists.sourceforge.net>",
+ devpath);
return rc;
}
prev parent reply other threads:[~2004-10-06 0:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-21 17:17 finally solve the bad sysfs-timing for all of us Kay Sievers
2004-09-21 20:04 ` Kay Sievers
2004-10-02 0:57 ` Kay Sievers
2004-10-05 20:51 ` Greg KH
2004-10-06 0:21 ` Kay Sievers [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=20041006002117.GA8387@vrfy.org \
--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 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).