[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6349D7A510622448B1BA0967850A8438011CBA5D@nasanexd02d.na.qualcomm.com>
Date: Wed, 19 Oct 2011 07:44:02 +0000
From: "Ren, Cloud" <cjren@....qualcomm.com>
To: David Miller <davem@...emloft.net>
CC: "Rodriguez, Luis" <rodrigue@....qualcomm.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [patch net-next]alx: Atheros AR8131/AR8151/AR8152/AR8161
Ethernet driver
Ok. What logging interfaces can I use? Are they dev_err, dev_info and dev_warn ? thanks
-----Original Message-----
From: David Miller [mailto:davem@...emloft.net]
Sent: Wednesday, October 19, 2011 3:33 PM
To: Ren, Cloud
Cc: Rodriguez, Luis; netdev@...r.kernel.org; linux-kernel@...r.kernel.org
Subject: Re: [patch net-next]alx: Atheros AR8131/AR8151/AR8152/AR8161 Ethernet driver
From: <cloud.ren@...eros.com>
Date: Wed, 19 Oct 2011 15:26:53 +0800
> +#define HW_PRINT(_klv, _fmt, _args...) \
> + if (ALX_HW_MSG_LV_##_klv || ALX_HW_MSG_LV_ALL) {\
> + printk(KERN_##_klv ALX_HW_MSG_PFX_NAME "%s: " _fmt, \
> + __func__, ## _args); \
> + }
Do not create your own network driver debugging facilities and macros for logging messages, we have rich debugging and logging level interfaces that network drivers can use exactly for this purpose.
--
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
Powered by blists - more mailing lists