From: Joe Perches <joe@perches.com>
To: netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH net-next 0/4] tulip: logging cleanups
Date: Mon, 9 May 2011 12:45:19 -0700 [thread overview]
Message-ID: <cover.1304970062.git.joe@perches.com> (raw)
More like 30 minutes.
Joe Perches (4):
tulip: xircom_cb: Convert #ifdef DEBUG blocks and enter/leave uses
tulip: Convert printks to netdev_<level>
tulip: Convert uses of KERN_DEBUG
tulip: Use pr_<level> where appropriate
drivers/net/tulip/21142.c | 14 +-
drivers/net/tulip/Makefile | 2 +
drivers/net/tulip/de2104x.c | 174 +++++++++++--------------
drivers/net/tulip/dmfe.c | 9 +-
drivers/net/tulip/eeprom.c | 4 +-
drivers/net/tulip/interrupt.c | 48 ++++----
drivers/net/tulip/media.c | 49 ++++----
drivers/net/tulip/pnic.c | 22 ++--
drivers/net/tulip/pnic2.c | 16 +-
drivers/net/tulip/timer.c | 47 +++----
drivers/net/tulip/tulip.h | 8 +-
drivers/net/tulip/tulip_core.c | 50 ++++----
drivers/net/tulip/uli526x.c | 65 +++------
drivers/net/tulip/winbond-840.c | 81 ++++++------
drivers/net/tulip/xircom_cb.c | 268 ++++++++++++--------------------------
15 files changed, 354 insertions(+), 503 deletions(-)
--
1.7.5.rc3.dirty
next reply other threads:[~2011-05-09 19:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-09 19:45 Joe Perches [this message]
2011-05-09 19:45 ` [PATCH net-next 1/4] tulip: xircom_cb: Convert #ifdef DEBUG blocks and enter/leave uses Joe Perches
2011-05-09 19:51 ` David Miller
2011-05-09 19:45 ` [PATCH net-next 2/4] tulip: Convert printks to netdev_<level> Joe Perches
2011-05-09 19:51 ` David Miller
2011-05-09 19:45 ` [PATCH net-next 3/4] tulip: Convert uses of KERN_DEBUG Joe Perches
2011-05-09 19:52 ` David Miller
2011-05-09 19:45 ` [PATCH net-next 4/4] tulip: Use pr_<level> where appropriate Joe Perches
2011-05-09 19:52 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2011-05-07 2:08 [PATCH net-next 0/4] tulip: logging cleanups Joe Perches
2011-05-09 18:47 ` 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=cover.1304970062.git.joe@perches.com \
--to=joe@perches.com \
--cc=linux-kernel@vger.kernel.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 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.