From: Mike Galbraith <efault@gmx.de>
To: LKML <linux-kernel@vger.kernel.org>
Subject: class_device_create_uevent/class_device_create_release log spamage
Date: Mon, 31 Jul 2006 07:31:29 +0200 [thread overview]
Message-ID: <1154323889.6235.12.camel@Homer.simpson.net> (raw)
In-Reply-To: <44BE5A07.9050706@gmx.net>
Greetings,
Presumably, these messages were added to find out who is using these.
root@Homer:..tmp/linux-2.6.18-rc3: dmesg|grep 'called for'|uniq -u|wc -l
1265
SuSE 10.1 uses heavily enough that I guess I'm going to have to increase
log buffer size to 18 be able to see a full message set after boot.
-Mike
prev parent reply other threads:[~2006-07-31 5:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-19 16:12 man-pages-2.36 is released Michael Kerrisk
2006-07-31 5:31 ` Mike Galbraith [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=1154323889.6235.12.camel@Homer.simpson.net \
--to=efault@gmx.de \
--cc=linux-kernel@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
Powered by JetHome