ocfs2-devel.oss.oracle.com archive mirror
 help / color / mirror / Atom feed
From: piaojun <piaojun@huawei.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 2/2] ocfs2/dlm: clean up unused stack variable in dlm_do_local_ast()
Date: Thu, 15 Mar 2018 21:02:32 +0800	[thread overview]
Message-ID: <5AAA6EE8.7010102@huawei.com> (raw)
In-Reply-To: <1521116681-14602-2-git-send-email-ge.changwei@h3c.com>



On 2018/3/15 20:24, Changwei Ge wrote:
> Signed-off-by: Changwei Ge <ge.changwei@h3c.com>
Acked-by: Jun Piao <piaojun@huawei.com>
> ---
>  fs/ocfs2/dlm/dlmast.c | 2 --
>  1 file changed, 2 deletions(-)
> 
> diff --git a/fs/ocfs2/dlm/dlmast.c b/fs/ocfs2/dlm/dlmast.c
> index fd6bbbb..39831fc 100644
> --- a/fs/ocfs2/dlm/dlmast.c
> +++ b/fs/ocfs2/dlm/dlmast.c
> @@ -224,14 +224,12 @@ void dlm_do_local_ast(struct dlm_ctxt *dlm, struct dlm_lock_resource *res,
>  		      struct dlm_lock *lock)
>  {
>  	dlm_astlockfunc_t *fn;
> -	struct dlm_lockstatus *lksb;
>  
>  	mlog(0, "%s: res %.*s, lock %u:%llu, Local AST\n", dlm->name,
>  	     res->lockname.len, res->lockname.name,
>  	     dlm_get_lock_cookie_node(be64_to_cpu(lock->ml.cookie)),
>  	     dlm_get_lock_cookie_seq(be64_to_cpu(lock->ml.cookie)));
>  
> -	lksb = lock->lksb;
>  	fn = lock->ast;
>  	BUG_ON(lock->ml.node != dlm->node_num);
>  
> 

  reply	other threads:[~2018-03-15 13:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-15 12:24 [Ocfs2-devel] [PATCH 1/2] ocfs2/dlm: clean up unused argument for dlm_destroy_recovery_area() Changwei Ge
2018-03-15 12:24 ` [Ocfs2-devel] [PATCH 2/2] ocfs2/dlm: clean up unused stack variable in dlm_do_local_ast() Changwei Ge
2018-03-15 13:02   ` piaojun [this message]
2018-03-15 13:01 ` [Ocfs2-devel] [PATCH 1/2] ocfs2/dlm: clean up unused argument for dlm_destroy_recovery_area() piaojun

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=5AAA6EE8.7010102@huawei.com \
    --to=piaojun@huawei.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).