From: David Howells <dhowells@redhat.com>
To: Rik van Riel <riel@redhat.com>
Cc: David Howells <dhowells@redhat.com>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH][1/2] fix for -mm add-sem_is_read-write_locked.patch
Date: Mon, 05 Sep 2005 15:14:10 +0100 [thread overview]
Message-ID: <1797.1125929650@warthog.cambridge.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0509050946190.4369@cuia.boston.redhat.com>
Rik van Riel <riel@redhat.com> wrote:
> I really shouldn't make patches like this in the morning on weekends,
> when I'm still sleepy. Well, here is the trivial fix...
That would seem to fix that bit.
David
prev parent reply other threads:[~2005-09-05 14:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-03 15:37 [PATCH][1/2] fix for -mm add-sem_is_read-write_locked.patch Rik van Riel
2005-09-05 9:48 ` David Howells
2005-09-05 13:42 ` Rik van Riel
2005-09-05 13:47 ` Rik van Riel
2005-09-05 14:14 ` David Howells [this message]
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=1797.1125929650@warthog.cambridge.redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.com \
/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