From: Goldwyn Rodrigues <rgoldwyn@suse.de>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 0/5] nocontrold: Eliminating ocfs2_controld v3
Date: Fri, 04 Oct 2013 10:01:34 -0500 [thread overview]
Message-ID: <524ED84E.4040109@suse.de> (raw)
In-Reply-To: <20131003112528.GR20001@suse.de>
On 10/03/2013 06:25 AM, Lars Marowsky-Bree wrote:
> On 2013-10-03T00:48:55, Goldwyn Rodrigues <rgoldwyn@suse.de> wrote:
>
> Hi Goldwyn,
>
> just a minor comment:
>
>> For backward compatibility, we are keeping the controld handling code. Once
>> enough time has passed we can remove a significant portion of the code.
>
> Can we add this to Documentation/fs/ocfs2.txt, or maybe print a one-time
> message on activating the deprecated mode with an intended removal date?
> (I'd propose end-of-2014.)
We already print a message in dmesg saying:
printk(KERN_NOTICE "ocfs2: You seem to be using an older "
"version of dlm_controld and/or ocfs2-tools."
" Please consider upgrading.\n");
Adding a date to this should not be a problem.
>
> And, perhaps, a compile-time option to disable this earlier, so that
> users can choose the stacks they want to build the kernel with.
>
This would a be a couple of ifdef's in user_cluster_connect(). What do
other ocfs2 developers feel about this?
--
Goldwyn
next prev parent reply other threads:[~2013-10-04 15:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 5:48 [Ocfs2-devel] [PATCH 0/5] nocontrold: Eliminating ocfs2_controld v3 Goldwyn Rodrigues
2013-10-03 11:25 ` Lars Marowsky-Bree
2013-10-04 15:01 ` Goldwyn Rodrigues [this message]
2013-10-08 0:06 ` Joel Becker
2013-10-08 20:02 ` Lars Marowsky-Bree
2013-10-03 20:30 ` Andrew Morton
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=524ED84E.4040109@suse.de \
--to=rgoldwyn@suse.de \
--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 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.