public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Christian Brauner <brauner@kernel.org>,
	Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
Cc: viro@zeniv.linux.org.uk, chuck.lever@oracle.com,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	Abaci Robot <abaci@linux.alibaba.com>
Subject: Re: [PATCH] fs/locks: Remove redundant assignment to cmd
Date: Thu, 09 Mar 2023 06:50:15 -0500	[thread overview]
Message-ID: <fd7e0f354da923ebb0cbe2c41188708e4d6c992a.camel@kernel.org> (raw)
In-Reply-To: <167835349787.767856.6018396733410513369.b4-ty@kernel.org>

On Thu, 2023-03-09 at 10:25 +0100, Christian Brauner wrote:
> From: Christian Brauner (Microsoft) <brauner@kernel.org>
> 
> 
> On Wed, 08 Mar 2023 15:13:16 +0800, Jiapeng Chong wrote:
> > Variable 'cmd' set but not used.
> > 
> > fs/locks.c:2428:3: warning: Value stored to 'cmd' is never read.
> > 
> > 
> 
> Seems unused for quite a while. I've picked this up since there's a few other
> trivial fixes I have pending. But I'm happy to drop this if you prefer this
> goes via the lock tree, Jeff.
> 
> [1/1] fs/locks: Remove redundant assignment to cmd
>       commit: dc592190a5543c559010e09e8130a1af3f9068d3

Thanks Christian,

I had already picked it into the locks-next branch (though I didn't get
a chance to reply and mention that), but I'll drop it and plan to let
you carry it.

Thanks,
-- 
Jeff Layton <jlayton@kernel.org>

  reply	other threads:[~2023-03-09 11:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-08  7:13 [PATCH] fs/locks: Remove redundant assignment to cmd Jiapeng Chong
2023-03-09  1:01 ` Chaitanya Kulkarni
2023-03-09  9:25 ` Christian Brauner
2023-03-09 11:50   ` Jeff Layton [this message]
2023-03-10  3:40     ` Al Viro
2023-03-10  8:52       ` Christian Brauner

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=fd7e0f354da923ebb0cbe2c41188708e4d6c992a.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=abaci@linux.alibaba.com \
    --cc=brauner@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=jiapeng.chong@linux.alibaba.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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