From: Rusty Russell <rusty@rustcorp.com.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Paul Menage <menage@google.com>,
linux-kernel@vger.kernel.org, Matthew Wilcox <matthew@wil.cx>,
"Randy.Dunlap" <rdunlap@xenotime.net>,
Andrew Morton <akpm@linux-foundation.org>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH] Introduce down_try() so we can move away from down_trylock()
Date: Mon, 4 Aug 2008 13:28:45 +1000 [thread overview]
Message-ID: <200808041328.45773.rusty@rustcorp.com.au> (raw)
In-Reply-To: <alpine.LFD.1.10.0808031034400.3668@nehalem.linux-foundation.org>
On Monday 04 August 2008 03:35:41 Linus Torvalds wrote:
> On Sun, 3 Aug 2008, Linus Torvalds wrote:
> > Anyway, I NAK'ed your patches. Deal with it.
>
> Btw, "dealing with it" can just be "don't bother".
Yes, let's not make a mountain out of a molehill.
Someone sent me a patch documenting the illogic of down_trylock(). I decided
to try to fix it rather than just bitch and moan.
Kernel coding involves occasionally getting fed a Linus-special shit sandwich
rant. I've long given up expecting a polite "No; please just replace them
all with mutexes" one-liner. I might have actually been shocked into doing
it.
Consider the patches forgotten,
Rusty.
next prev parent reply other threads:[~2008-08-04 3:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 0:15 [PATCH] Introduce down_try() so we can move away from down_trylock() Rusty Russell
2008-07-29 0:27 ` Paul Menage
2008-07-29 13:01 ` Rusty Russell
2008-07-29 16:21 ` Randy Dunlap
2008-07-29 23:56 ` Rusty Russell
2008-08-01 17:26 ` Linus Torvalds
2008-08-01 17:40 ` Andrew Morton
2008-08-01 18:22 ` Linus Torvalds
2008-08-03 8:33 ` Rusty Russell
2008-08-03 13:07 ` Matthew Wilcox
2008-08-03 17:33 ` Linus Torvalds
2008-08-03 17:35 ` Linus Torvalds
2008-08-04 3:28 ` Rusty Russell [this message]
2008-08-04 5:53 ` Linus Torvalds
2008-08-04 7:57 ` Rusty Russell
2008-08-04 8:45 ` Alan Cox
2008-08-04 11:43 ` 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=200808041328.45773.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=menage@google.com \
--cc=rdunlap@xenotime.net \
--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.