netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: cjren@qca.qualcomm.com
Cc: rodrigue@qca.qualcomm.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [patch net-next]alx: Atheros AR8131/AR8151/AR8152/AR8161 Ethernet driver
Date: Wed, 19 Oct 2011 03:50:00 -0400 (EDT)	[thread overview]
Message-ID: <20111019.035000.931404890148181821.davem@davemloft.net> (raw)
In-Reply-To: <6349D7A510622448B1BA0967850A8438011CBA5D@nasanexd02d.na.qualcomm.com>

From: "Ren, Cloud" <cjren@qca.qualcomm.com>
Date: Wed, 19 Oct 2011 07:44:02 +0000

> Ok. What logging interfaces can I use? Are they dev_err, dev_info and dev_warn ? thanks

netif_*(), they check netif_msg_*() to see if the particular kind
of logging message is enabled or not, and this can be set dynamically
if you code your driver to properly set netdev->msg_enable.

Use other drivers as examples.

  reply	other threads:[~2011-10-19  7:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-19  7:26 [patch net-next]alx: Atheros AR8131/AR8151/AR8152/AR8161 Ethernet driver cloud.ren
2011-10-19  7:33 ` David Miller
2011-10-19  7:44   ` Ren, Cloud
2011-10-19  7:50     ` David Miller [this message]
2011-10-19  7:53       ` Ren, Cloud
2011-10-19  7:56     ` Joe Perches
2011-10-19 22:21 ` Francois Romieu
2011-10-19 22:59   ` Joe Perches
2011-10-20  7:29   ` Ren, Cloud
2011-10-20  8:48     ` David Miller
2011-10-28  2:56   ` Joe Perches
  -- strict thread matches above, loose matches on Subject: below --
2011-10-20  6:46 cloud.ren
2011-10-20  8:45 ` David Miller
2011-10-20  9:00   ` Joe Perches
2011-10-20  9:23   ` Ren, Cloud
2011-10-20  9:25     ` David Miller
2011-10-20  9:48       ` Ren, Cloud
2011-10-20 20:33         ` Luis R. Rodriguez
2011-10-21  2:21           ` Ren, Cloud
2011-10-21  2:36             ` Luis R. Rodriguez

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=20111019.035000.931404890148181821.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=cjren@qca.qualcomm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rodrigue@qca.qualcomm.com \
    /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).