netdev - Re: [PATCH] [IRDA] irda_init() nuke useless debug printk

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20080212.181742.150703641.davem@davemloft.net>
Date:	Tue, 12 Feb 2008 18:17:42 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	max@...o.at
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH] [IRDA] irda_init() nuke useless debug printk

From: maximilian attems <max@...o.at>
Date: Tue, 12 Feb 2008 11:30:47 +0100

> irda_init()
> dmesg line is not really informative, thus remove it.
> There are better ways to know that a module is loaded.
> 
> Seen on a debian config with IRDA_DEBUG enabled.
> 
> Signed-off-by: maximilian attems <max@...o.at>

Well if you look at how IRDA_DEBUG is predominantly used,
it's a function tracer, and that's exactly how it's being
used here.

Either we decide that this is OK and leave it there, or
we start moving the whole IRDA tree over to not do this.
Not something in between.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html