From: David Miller <davem@davemloft.net>
To: joe@perches.com
Cc: jeffrey.t.kirsher@intel.com, netdev@vger.kernel.org,
jesse.brandeburg@intel.com, bruce.w.allan@intel.com,
alexander.h.duyck@intel.com, peter.p.waskiewicz.jr@intel.com,
john.ronciak@intel.com, gallatin@myri.com, brice@myri.com,
linux-kernel@vger.kernel.org, e1000-devel@lists.sourceforge.net
Subject: Re: [PATCH net-next] drivers/net/e100.c: Use pr_<level> and netif_<level>
Date: Tue, 16 Mar 2010 21:31:49 -0700 (PDT) [thread overview]
Message-ID: <20100316.213149.00701940.davem@davemloft.net> (raw)
In-Reply-To: <1267478181.12641.142.camel@Joe-Laptop.home>
From: Joe Perches <joe@perches.com>
Date: Mon, 01 Mar 2010 13:16:21 -0800
> Convert DPRINTK, commonly used for debugging, to netif_<level>
> Remove #define PFX
> Use #define pr_fmt
> Consistently use no periods for non-sentence logging messages
>
> Signed-off-by: Joe Perches <joe@perches.com>
Applied.
WARNING: multiple messages have this Message-ID (diff)
From: David Miller <davem@davemloft.net>
To: joe@perches.com
Cc: e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org,
bruce.w.allan@intel.com, jesse.brandeburg@intel.com,
linux-kernel@vger.kernel.org, john.ronciak@intel.com,
jeffrey.t.kirsher@intel.com, gallatin@myri.com, brice@myri.com
Subject: Re: [PATCH net-next] drivers/net/e100.c: Use pr_<level> and netif_<level>
Date: Tue, 16 Mar 2010 21:31:49 -0700 (PDT) [thread overview]
Message-ID: <20100316.213149.00701940.davem@davemloft.net> (raw)
In-Reply-To: <1267478181.12641.142.camel@Joe-Laptop.home>
From: Joe Perches <joe@perches.com>
Date: Mon, 01 Mar 2010 13:16:21 -0800
> Convert DPRINTK, commonly used for debugging, to netif_<level>
> Remove #define PFX
> Use #define pr_fmt
> Consistently use no periods for non-sentence logging messages
>
> Signed-off-by: Joe Perches <joe@perches.com>
Applied.
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
next prev parent reply other threads:[~2010-03-17 4:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 2:56 [PATCH net-next 0/7] drivers/net conversions to netdev_<level>, etc Joe Perches
2010-02-23 2:56 ` Joe Perches
2010-02-23 2:56 ` [PATCH net-next 1/7] drivers/net/chelsio: Use pr_<level>, netif_msg_<type> Joe Perches
2010-02-26 9:40 ` David Miller
2010-02-23 2:56 ` [PATCH net-next 2/7] drivers/net/myri10ge: Use pr_<level> and netdev_<level> Joe Perches
2010-02-26 9:40 ` David Miller
2010-02-23 2:56 ` [PATCH net-next 3/7] drivers/net/ixgbe: Use pr_<level> and netif_<level> Joe Perches
2010-02-23 2:56 ` Joe Perches
2010-02-23 2:57 ` [PATCH net-next 4/7] drivers/net/ixgb: Use pr_<level> and netdev_<level> Joe Perches
2010-02-23 2:57 ` Joe Perches
2010-02-23 2:57 ` [PATCH net-next 5/7] drivers/net/e1000: Use pr_<level> and netif_<level> Joe Perches
2010-02-23 2:57 ` Joe Perches
2010-02-23 2:57 ` [PATCH net-next 6/7] drivers/net/e1000e: Use pr_<level> and netdev_<level> Joe Perches
2010-02-23 2:57 ` Joe Perches
2010-02-23 19:17 ` Allan, Bruce W
2010-02-23 19:17 ` Allan, Bruce W
2010-02-23 2:57 ` [PATCH net-next 7/7] drivers/net/igb: Use netdev_<level> Joe Perches
2010-02-23 2:57 ` Joe Perches
2010-02-24 2:33 ` [PATCH net-next 0/7] drivers/net conversions to netdev_<level>, etc Jeff Kirsher
2010-02-24 2:33 ` Jeff Kirsher
2010-03-01 21:16 ` [PATCH net-next] drivers/net/e100.c: Use pr_<level> and netif_<level> Joe Perches
2010-03-17 4:31 ` David Miller [this message]
2010-03-17 4:31 ` David Miller
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=20100316.213149.00701940.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexander.h.duyck@intel.com \
--cc=brice@myri.com \
--cc=bruce.w.allan@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=gallatin@myri.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=joe@perches.com \
--cc=john.ronciak@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.