From: "Ray Lee" <ray-lk@madrabbit.org>
To: "Larry Finger" <Larry.Finger@lwfinger.net>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: SoftMAC: Getting essid from req_essid
Date: Fri, 30 Nov 2007 15:06:32 -0800 [thread overview]
Message-ID: <2c0942db0711301506k7e154b76kc1fc99c189f68a3d@mail.gmail.com> (raw)
Hey there Larry, all,
git blame fingered commit id efe870f9 (from Larry) for adding a couple
of fairly harmless looking messages to
net/ieee80211/softmac/ieee80211softmac_wx.c . The problem is that one
of them is clogging up my syslog at the tune of once a second or so
("SoftMAC: Getting essid from req_essid"), and rolling everything else
out of my dmesg.
I just rebooted into 2.6.23-rc3+some, and after 36 minutes of uptime I
already have:
$ dmesg | cut -d ']' -f2- | sort | uniq -c | sort -nr | head -3
1047 SoftMAC: Getting essid from req_essid
38 SoftMAC: Getting essid from associate_essid
22 SoftMAC: Scanning finished: scanned 13 channels starting with channel 1
Is the message important for debugging, or can I make a patch to yank
the silly thing?
Ray
next reply other threads:[~2007-11-30 23:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-30 23:06 Ray Lee [this message]
2007-12-03 23:31 ` SoftMAC: Getting essid from req_essid Larry Finger
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=2c0942db0711301506k7e154b76kc1fc99c189f68a3d@mail.gmail.com \
--to=ray-lk@madrabbit.org \
--cc=Larry.Finger@lwfinger.net \
--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;
as well as URLs for NNTP newsgroup(s).