From: Tom Vier <tmv@comcast.net>
To: "Vladimir V. Saveliev" <vs@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: Re: 2.6.16 + reiser4 -2 patch = gcc error
Date: Thu, 18 May 2006 15:01:52 -0400 [thread overview]
Message-ID: <20060518190152.GB25823@zero> (raw)
In-Reply-To: <1147945452.6417.24.camel@tribesman.namesys.com>
On Thu, May 18, 2006 at 01:44:12PM +0400, Vladimir V. Saveliev wrote:
> I guess you got broken lines 485 and 507 in file
> fs/reiser4/plugin/file_ops_readdir.c
>
> Here is what you should have:
> 485: mutex_lock(&inode->i_mutex);
> 507: mutex_unlock(&inode->i_mutex);
Actually, it was my fault. I had forgotten to apply the 2.6.15->.16 patch.
Thanks for you help, tho.
--
Tom Vier <tmv@comcast.net>
DSA Key ID 0x15741ECE
prev parent reply other threads:[~2006-05-18 19:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-17 19:08 2.6.16 + reiser4 -2 patch = gcc error Tom Vier
2006-05-18 9:44 ` Vladimir V. Saveliev
2006-05-18 19:01 ` Tom Vier [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=20060518190152.GB25823@zero \
--to=tmv@comcast.net \
--cc=reiserfs-list@namesys.com \
--cc=vs@namesys.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 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.