From: Patrick Pannuto <ppannuto@codeaurora.org>
To: linux-kernel@vger.kernel.org
Cc: ppannuto@codeaurora.org, apw@canonical.com, corbet@lwn.net,
arjan@linux.intel.com, linux-arm-msm@vger.kernel.org
Subject: [PATCH v3 0/4] Add usleep_range
Date: Mon, 2 Aug 2010 15:01:03 -0700 [thread overview]
Message-ID: <1280786467-26999-1-git-send-email-ppannuto@codeaurora.org> (raw)
Changes from v2:
* Remove usleep API
It seemed the weak consensus that the best way to
force callers to consider the cost / implications
of the underlying hrtimers was to leave only the
range API as an option. Given the dangers of an
implicit slack coupled with the potential
proliferation of interrupts with no slack, forcing
callers to supply a range seems the best choice.
* Documentation updated to reflect changes
* Fix checkpatch warnings to point to the correct file
[PATCH v3 1/4] timer: Added usleep_range timer
[PATCH v3 2/4] Documentation: Add timers/timers-howto.txt
[PATCH v3 3/4] Checkpatch: prefer usleep_range over udelay
[PATCH v3 4/4] Checkpatch: warn about unexpectedly long msleep's
next reply other threads:[~2010-08-02 22:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 22:01 Patrick Pannuto [this message]
2010-08-02 22:01 ` [PATCH 1/4] timer: Added usleep_range timer Patrick Pannuto
2010-08-03 22:51 ` Andrew Morton
2010-08-02 22:01 ` [PATCH 2/4] Documentation: Add timers/timers-howto.txt Patrick Pannuto
2010-08-02 22:01 ` [PATCH 3/4] Checkpatch: prefer usleep_range over udelay Patrick Pannuto
2010-08-02 22:01 ` [PATCH 4/4] Checkpatch: warn about unexpectedly long msleep's Patrick Pannuto
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=1280786467-26999-1-git-send-email-ppannuto@codeaurora.org \
--to=ppannuto@codeaurora.org \
--cc=apw@canonical.com \
--cc=arjan@linux.intel.com \
--cc=corbet@lwn.net \
--cc=linux-arm-msm@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).