virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Manuel Zerpies <manuel.f.zerpies@ww.stud.uni-erlangen.de>
To: "David S. Miller" <davem@davemloft.net>,
	Steve Wise <swise@chelsio.com>, Roland Dreier <roland@kernel.org>,
	Sean Hefty <sean.hefty@intel.com>, Hal Rosenstock <hal.rosenst>
Subject: [PATCH 00/11] Replace printk_rateilimit() with printk_ratelimited()
Date: Thu, 16 Jun 2011 14:06:04 +0200	[thread overview]
Message-ID: <cover.1308142053.git.manuel.f.zerpies@ww.stud.uni-erlangen.de> (raw)

Hi,

since the printk_ratelimit() function shouldn't be used anymore, I replaced it
in a few files with printk_ratelimited().

If you wish some more patches I can send more in.

Greets,
Manu

Manuel Zerpies (11):
  drivers/ide: use printk_ratelimited() instead of printk_ratelimit()
  drivers/tty: use printk_ratelimited() instead of printk_ratelimit()
  net/can: use printk_ratelimited() instead of printk_ratelimit()
  net/rds: use prink_ratelimited() instead of printk_ratelimit()
  RDMA/hw/cxgb4: use printk_ratelimited() instead of printk_ratelimit()
  drivers/net: use printk_ratelimited() instead of printk_ratelimit()
  drivers/usb/atm: use printk_ratelimited() instead of
    printk_ratelimit()
  [SCSI] tcm_fc: use printk_ratelimited() instead of printk_ratelimit()
  xen/xenbus: use printk_ratelimited() instead of printk_ratelimit()
  wusb: use printk_ratelimited() instead of printk_ratelimit()
  usb/class: use printk_ratelimited() instead of printk_ratelimit()

 drivers/ide/ide-atapi.c                |    4 ++--
 drivers/infiniband/hw/cxgb4/resource.c |    9 +++++----
 drivers/net/sc92031.c                  |   16 ++++++----------
 drivers/target/tcm_fc/tfc_io.c         |    4 ++--
 drivers/tty/moxa.c                     |    5 +++--
 drivers/tty/mxser.c                    |    4 ++--
 drivers/tty/tty_io.c                   |    4 ++--
 drivers/usb/atm/usbatm.c               |    4 ++--
 drivers/usb/class/usblp.c              |    7 +++----
 drivers/usb/wusbcore/wa-xfer.c         |    7 +++----
 drivers/xen/xenbus/xenbus_xs.c         |    4 ++--
 net/can/af_can.c                       |    5 +++--
 net/rds/bind.c                         |    4 ++--
 net/rds/ib_cm.c                        |    6 +++---
 net/rds/ib_send.c                      |    4 ++--
 net/rds/iw_cm.c                        |    9 ++++-----
 net/rds/iw_rdma.c                      |    9 +++++----
 net/rds/iw_send.c                      |    4 ++--
 net/rds/send.c                         |    7 +++----
 19 files changed, 56 insertions(+), 60 deletions(-)

-- 
1.7.4.1

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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-16 12:06 Manuel Zerpies [this message]
2011-06-16 12:14 ` [PATCH 09/11] xen/xenbus: use printk_ratelimited() instead of printk_ratelimit() Manuel Zerpies
     [not found] ` <d2bc569719b3b1d8271d1f4b2c4080bbc7527e04.1308142053.git.manuel.f.zerpies@ww.stud.uni-erlangen.de>
2011-06-16 21:00   ` Jeremy Fitzhardinge
     [not found]   ` <4DFA6EF7.9060702@goop.org>
2011-06-16 23:44     ` Joe Perches

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.1308142053.git.manuel.f.zerpies@ww.stud.uni-erlangen.de \
    --to=manuel.f.zerpies@ww.stud.uni-erlangen.de \
    --cc=davem@davemloft.net \
    --cc=roland@kernel.org \
    --cc=sean.hefty@intel.com \
    --cc=swise@chelsio.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).