All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: netdev@vger.kernel.org, e1000-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: [PATCH net-next 0/5] intel: Logging cleanups
Date: Wed, 12 Oct 2011 09:18:05 -0700	[thread overview]
Message-ID: <cover.1318436085.git.joe@perches.com> (raw)

Just some conversions of printks to pr_<level>
and some trivial defect corrections.

Joe Perches (5):
  e1000e: Convert printks to pr_<level>
  ixgbevf: Convert printks to pr_<level>
  igbvf: Convert printks to pr_<level>
  igb: Convert printks to pr_<level>
  igb: Convert bare printk to pr_notice

 drivers/net/ethernet/intel/e1000e/netdev.c        |  232 +++++++++------------
 drivers/net/ethernet/intel/igb/e1000_82575.c      |    5 +-
 drivers/net/ethernet/intel/igb/igb_main.c         |  155 +++++++--------
 drivers/net/ethernet/intel/igbvf/netdev.c         |   14 +-
 drivers/net/ethernet/intel/ixgbevf/ethtool.c      |    6 +-
 drivers/net/ethernet/intel/ixgbevf/ixgbevf_main.c |   26 ++--
 6 files changed, 201 insertions(+), 237 deletions(-)

-- 
1.7.6.405.gc1be0


             reply	other threads:[~2011-10-12 16:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-12 16:18 Joe Perches [this message]
2011-10-12 16:18 ` [PATCH net-next 1/5] e1000e: Convert printks to pr_<level> Joe Perches
2011-10-12 16:18 ` [PATCH net-next 2/5] ixgbevf: " Joe Perches
2011-10-12 16:18 ` [PATCH net-next 3/5] igbvf: " Joe Perches
2011-10-12 16:18 ` [PATCH net-next 4/5] igb: " Joe Perches
2011-10-12 16:18 ` [PATCH net-next 5/5] igb: Convert bare printk to pr_notice Joe Perches
2011-10-12 22:56 ` [PATCH net-next 0/5] intel: Logging cleanups Jeff Kirsher

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.1318436085.git.joe@perches.com \
    --to=joe@perches.com \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=jeffrey.t.kirsher@intel.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.