mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
	ccaulfie@redhat.com, teigland@redhat.com
Cc: cluster-devel@redhat.com, linux-kernel@vger.kernel.org,
	kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] dlm: fix a typo
Date: Mon, 22 Jul 2019 08:55:11 +0200	[thread overview]
Message-ID: <e561b3e8-e3da-b81c-2b06-3be4fa3d1c61@metux.net> (raw)
In-Reply-To: <20190721104322.30019-1-christophe.jaillet@wanadoo.fr>

On 21.07.19 12:43, Christophe JAILLET wrote:
> s/locksapce/lockspace
> 
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> ---
>   fs/dlm/lockspace.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/fs/dlm/lockspace.c b/fs/dlm/lockspace.c
> index 00fa700f4e83..9c95df8a36e9 100644
> --- a/fs/dlm/lockspace.c
> +++ b/fs/dlm/lockspace.c
> @@ -870,7 +870,7 @@ static int release_lockspace(struct dlm_ls *ls, int force)
>    * until this returns.
>    *
>    * Force has 4 possible values:
> - * 0 - don't destroy locksapce if it has any LKBs
> + * 0 - don't destroy lockspace if it has any LKBs
>    * 1 - destroy lockspace if it has remote LKBs but not if it has local LKBs
>    * 2 - destroy lockspace regardless of LKBs
>    * 3 - destroy lockspace as part of a forced shutdown
> 

Reviewed-By: Enrico Weigelt <info@metux.net>


-- 
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@metux.net -- +49-151-27565287

      reply	other threads:[~2019-07-22  6:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-21 10:43 Christophe JAILLET
2019-07-22  6:55 ` Enrico Weigelt, metux IT consult [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=e561b3e8-e3da-b81c-2b06-3be4fa3d1c61@metux.net \
    --to=lkml@metux.net \
    --cc=ccaulfie@redhat.com \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=cluster-devel@redhat.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=teigland@redhat.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

all inboxes | Powered by JetHome®