mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Vasquez <andrew.vasquez@qlogic.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] Introduce mutex_lock_timeout
Date: Mon, 20 Nov 2006 13:13:47 -0800	[thread overview]
Message-ID: <20061120211347.GH11420@andrew-vasquezs-computer.local> (raw)
In-Reply-To: <20061109182721.GN16952@parisc-linux.org>

On Thu, 09 Nov 2006, Matthew Wilcox wrote:

> We have a couple of places in the tree that really could do with a
> down_timeout() function.  I noticed it in qla2xxx and ACPI, but maybe
> there are others that don't have the courtesy of putting "I wish we had
> a down_timeout" comment beside their implementation.

I'm testing this with qla2xxx...  btw: there's a minor cut-n-paste
error in the x86_64 variant where you forgot a ',' (comma).

> diff --git a/include/asm-x86_64/mutex.h b/include/asm-x86_64/mutex.h
> index 16396b1..18668fa 100644
> --- a/include/asm-x86_64/mutex.h
> +++ b/include/asm-x86_64/mutex.h
> @@ -46,11 +46,11 @@ do {									\
>   * or anything the slow path function returns
>   */
>  static inline int
> -__mutex_fastpath_lock_retval(atomic_t *count,
> -			     int fastcall (*fail_fn)(atomic_t *))
> +__mutex_fastpath_lock_retval(atomic_t *count, long jiffies
> +			     int fastcall (*fail_fn)(atomic_t *, long))

should be:

	+__mutex_fastpath_lock_retval(atomic_t *count, long jiffies,
	+			     int fastcall (*fail_fn)(atomic_t *, long))

  parent reply	other threads:[~2006-11-20 21:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-09 18:27 Matthew Wilcox
2006-11-09 18:30 ` [PATCH 2/2] Use mutex_lock_timeout in qla2xxx driver Matthew Wilcox
2006-11-20 21:21   ` Andrew Vasquez
2006-11-20 21:13 ` Andrew Vasquez [this message]
2006-11-25  3:55 ` [PATCH 1/2] Introduce mutex_lock_timeout Matthew Wilcox
2006-11-25 16:00   ` Ingo Oeser
2006-11-25 16:32     ` Matthew Wilcox
2006-11-26 11:00       ` Ingo Oeser

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=20061120211347.GH11420@andrew-vasquezs-computer.local \
    --to=andrew.vasquez@qlogic.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@wil.cx \
    /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

all inboxes | Powered by JetHome®