From: Marc Dietrich <marvin24@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] replace large udelay by mdelay
Date: Wed, 22 May 2013 21:48:40 +0200 [thread overview]
Message-ID: <cover.1369251478.git.marvin24@gmx.de> (raw)
bad_udelay is generated on distro kernels which often enable all kinds
of drivers. ARM has a max udelay of 2000, so this patchset converts large
udelays to mdelays. This may also be observed using all_modconfig.
Marc Dietrich (2):
SCSI: nsp32: replace large udelay by mdelay
nouveau: replace large udelay by mdelay
drivers/gpu/drm/nouveau/core/engine/disp/dacnv50.c | 3 ++-
drivers/scsi/nsp32.c | 2 +-
drivers/scsi/nsp32.h | 2 +-
3 files changed, 4 insertions(+), 3 deletions(-)
--
1.7.9.5
next reply other threads:[~2013-05-22 19:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 19:48 Marc Dietrich [this message]
2013-05-22 19:48 ` [PATCH 1/2] SCSI: nsp32: replace large udelay by mdelay Marc Dietrich
2013-05-22 20:33 ` Marc Dietrich
2013-05-27 9:04 ` Marc Dietrich
2013-05-22 19:48 ` [PATCH 2/2] nouveau: " Marc Dietrich
2013-05-22 20:08 ` David Daney
2013-05-22 20:33 ` Marc Dietrich
2013-05-27 9:10 ` Marc Dietrich
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.1369251478.git.marvin24@gmx.de \
--to=marvin24@gmx.de \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox