From: Florian Westphal <fw-tipc@strlen.de>
To: tipc-discussion@lists.sourceforge.net
Cc: Matthias Kaehlcke <matthias@kaehlcke.net>,
per.liden@ericsson.com, jon.maloy@ericsson.com,
allan.stephens@windriver.com, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org
Subject: Re: [tipc-discussion] [PATCH] TIPC Protocol: Convert tsock->sem in a mutex
Date: Sun, 2 Mar 2008 23:16:23 +0100 [thread overview]
Message-ID: <20080302221623.GE14859@Chamillionaire.breakpoint.cc> (raw)
In-Reply-To: <20080302183637.GB2783@traven>
Matthias Kaehlcke <matthias@kaehlcke.net> wrote:
> TIPC Protocol: The semaphore tsock->sem is used as mutex, convert it
> to the mutex API
The locking mechanism was re-done in TIPC 1.7.X, and
AFAIK Allan Stephens is working on submitting
the current TIPC version for inclusion in 2.6.26.
So it probably doesn't make much sense to merge this patch
(even though it looks correct).
Sorry.
next prev parent reply other threads:[~2008-03-02 22:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-02 18:36 Matthias Kaehlcke
2008-03-02 22:16 ` Florian Westphal [this message]
2008-03-04 7:37 ` David Miller
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=20080302221623.GE14859@Chamillionaire.breakpoint.cc \
--to=fw-tipc@strlen.de \
--cc=akpm@linux-foundation.org \
--cc=allan.stephens@windriver.com \
--cc=jon.maloy@ericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias@kaehlcke.net \
--cc=per.liden@ericsson.com \
--cc=tipc-discussion@lists.sourceforge.net \
/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®