From: Krzysiek Pawlik <krzysiek.pawlik@people.pl>
To: linux-hotplug@vger.kernel.org
Subject: Re: wait_for_sysfs - report
Date: Thu, 09 Dec 2004 22:12:23 +0000 [thread overview]
Message-ID: <41B8CDC7.1020906@people.pl> (raw)
In-Reply-To: <41B8C951.3020508@people.pl>
Kay Sievers on 12/09/04 23:07 wrote:
> We got several reports like that. I've had the same problem here but
> it's gone with kernel 2.6.10*, so I never looked into the real reason
> for it.
I don't play with -rc series kernels due to that I need working system
to work. I simply don't have time to compile the kernel few times to
test it. I'll wait for stable 2.6.10.
>>>Hi. While playing around with GigaPod (external USB connected disk
>>>enclosure) I've got this in messages:
>>Please upgrade to 048.
>
> Yeah, we don't print anything from v047 on.
> I've had enough fun with that for now :)
"don't print" - it supresses the message and ignores the problem?
As soon as 048 gets to Gentoo's portage tree I'll upgrade.
--
Krzysiek 'Nelchael' Pawlik RLU #322999 krzysiek.pawlik@people.pl
gentoo base system - kernel 2.6.9-ck3 GPG:0x7E226904
http://fatcat.ftj.agh.edu.pl/~nelchael/
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
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-12-09 22:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-09 21:53 wait_for_sysfs - report Krzysiek Pawlik
2004-12-09 22:00 ` Marco d'Itri
2004-12-09 22:07 ` Kay Sievers
2004-12-09 22:12 ` Krzysiek Pawlik [this message]
2004-12-09 22:17 ` Kay Sievers
2004-12-09 22:18 ` Krzysiek Pawlik
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=41B8CDC7.1020906@people.pl \
--to=krzysiek.pawlik@people.pl \
--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.