All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Walker <dwalker@mvista.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Christoph Hellwig <hch@infradead.org>,
	Matthew Wilcox <matthew@wil.cx>
Subject: Re: [PATCH] Introduce down_nowait()
Date: Wed, 21 May 2008 10:04:58 -0700	[thread overview]
Message-ID: <1211389499.18130.53.camel@localhost.localdomain> (raw)
In-Reply-To: <200805211756.04731.rusty@rustcorp.com.au>


On Wed, 2008-05-21 at 17:56 +1000, Rusty Russell wrote:


> Subject: [PATCH] Introduce down_try()
> 
> I planned on removing the much-disliked down_trylock() (with its
> backwards return codes) in 2.6.27, but it's creating something of a
> logjam with other patches in -mm and linux-next.
> 
> Andrew suggested introducing "down_try" as a wrapper now, to make
> the transition easier.

I must be missing something critical, but what's the logjam this is
causing?

Daniel


  reply	other threads:[~2008-05-21 17:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-21  6:00 [PATCH] Introduce down_nowait() Rusty Russell
2008-05-21  6:29 ` Andrew Morton
2008-05-21  7:56   ` Rusty Russell
2008-05-21 17:04     ` Daniel Walker [this message]
2008-05-22  8:56       ` Rusty Russell
2008-05-22 15:48         ` Daniel Walker
2008-05-23  0:52           ` Rusty Russell
2008-05-21  8:04   ` Christoph Hellwig
2008-05-21  8:19     ` Andrew Morton
2008-05-21 12:09       ` Rusty Russell

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=1211389499.18130.53.camel@localhost.localdomain \
    --to=dwalker@mvista.com \
    --cc=akpm@linux-foundation.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=rusty@rustcorp.com.au \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.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.