From: Joel Becker <Joel.Becker@oracle.com>
To: Adrian Bunk <bunk@kernel.org>
Cc: Mark Fasheh <mfasheh@suse.com>,
ocfs2-devel@oss.oracle.com, linux-kernel@vger.kernel.org
Subject: [Ocfs2-devel] [2.6 patch] ocfs2: rename user_stack{,_ops}
Date: Tue, 20 May 2008 16:53:01 -0700 [thread overview]
Message-ID: <20080520235301.GM26609@mail.oracle.com> (raw)
In-Reply-To: <20080520225509.GD16264@cs181133002.pp.htv.fi>
On Wed, May 21, 2008 at 01:55:09AM +0300, Adrian Bunk wrote:
> This patch therefore prefixes the user_stack{,_ops} names with ocfs2_
Thanks for reporting this. Al already reported it and a fix is
in ocfs2.git. We change the name entirely so that grep of user_stack
doesn't match it at all.
Joel
--
"Nobody loves me,
Nobody seems to care.
Troubles and worries, people,
You know I've had my share."
Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127
prev parent reply other threads:[~2008-05-20 23:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-20 22:55 [Ocfs2-devel] [2.6 patch] ocfs2: rename user_stack{,_ops} Adrian Bunk
2008-05-20 23:53 ` Joel Becker [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=20080520235301.GM26609@mail.oracle.com \
--to=joel.becker@oracle.com \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfasheh@suse.com \
--cc=ocfs2-devel@oss.oracle.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;
as well as URLs for NNTP newsgroup(s).