From: Joel Becker <jlbec@evilplan.org>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [RESENT PATCH 3/4] ocfs2: fix a comments typo at o2quo_hb_still_up()
Date: Mon, 1 Jul 2013 15:59:46 -0700 [thread overview]
Message-ID: <20130701225946.GD965@localhost> (raw)
In-Reply-To: <51CE5C0A.7030105@oracle.com>
On Sat, Jun 29, 2013 at 12:01:14PM +0800, Jeff Liu wrote:
> From: Jie Liu <jeff.liu@oracle.com>
>
> Fix a comments typo at o2quo_hb_still_up()
>
> Signed-off-by: Jie Liu <jeff.liu@oracle.com>
Acked-by: Joel Becker <jlbec@evilplan.org>
> ---
> fs/ocfs2/cluster/quorum.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/ocfs2/cluster/quorum.c b/fs/ocfs2/cluster/quorum.c
> index c19897d..1ec141e 100644
> --- a/fs/ocfs2/cluster/quorum.c
> +++ b/fs/ocfs2/cluster/quorum.c
> @@ -264,7 +264,7 @@ void o2quo_hb_still_up(u8 node)
> /* This is analogous to hb_up. as a node's connection comes up we delay the
> * quorum decision until we see it heartbeating. the hold will be droped in
> * hb_up or hb_down. it might be perpetuated by con_err until hb_down. if
> - * it's already heartbeating we we might be dropping a hold that conn_up got.
> + * it's already heartbeating we might be dropping a hold that conn_up got.
> * */
> void o2quo_conn_up(u8 node)
> {
> --
> 1.7.9.5
>
> _______________________________________________
> Ocfs2-devel mailing list
> Ocfs2-devel at oss.oracle.com
> https://oss.oracle.com/mailman/listinfo/ocfs2-devel
--
"If you took all of the grains of sand in the world, and lined
them up end to end in a row, you'd be working for the government!"
- Mr. Interesting
http://www.jlbec.org/
jlbec at evilplan.org
prev parent reply other threads:[~2013-07-01 22:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-29 4:01 [Ocfs2-devel] [RESENT PATCH 3/4] ocfs2: fix a comments typo at o2quo_hb_still_up() Jeff Liu
2013-07-01 22:59 ` 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=20130701225946.GD965@localhost \
--to=jlbec@evilplan.org \
--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.