From: Pavel Roskin <proski@gnu.org>
To: Jason Lunz <lunz@falooley.org>
Cc: netdev@vger.kernel.org, ipw3945-devel@lists.sourceforge.net
Subject: Re: iwlwifi initial bugs/thanks
Date: Tue, 13 Feb 2007 15:18:36 -0500 [thread overview]
Message-ID: <1171397916.2414.31.camel@dv> (raw)
In-Reply-To: <20070213191313.GA2427@metaxa.reflex>
On Tue, 2007-02-13 at 14:13 -0500, Jason Lunz wrote:
> The "_rename" suffix is an indication that you have udev rules that are
> attempting to assign the same name to two different netdevs. Try to
> disable udev device renaming, or make the rules more specific.
>
> The attached kernel patch makes it easier to figure out what udev is
> trying to do in situations like yours. It keeps getting rejected from
> linux upstream, but that could change with enough encouragement.
I think it's a good idea. Many drivers use the device name in the
diagnostic messages. What's the point in seeing "wlan0: buffer
overflow" if there is no way to find out from the log what that "wlan0"
used to be?
> + if (strncmp(newname, dev->name, IFNAMSIZ))
> + printk(KERN_INFO "%s renamed to %s\n", dev->name, newname);
I think KERN_INFO is the right level, but maybe KERN_DEBUG would be more
readily accepted.
--
Regards,
Pavel Roskin
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
prev parent reply other threads:[~2007-02-13 20:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1171382436.12035.38.camel@localhost>
2007-02-13 19:13 ` iwlwifi initial bugs/thanks Jason Lunz
2007-02-13 20:18 ` Pavel Roskin [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=1171397916.2414.31.camel@dv \
--to=proski@gnu.org \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=lunz@falooley.org \
--cc=netdev@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).