public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Byongho Lee <bhlee.kernel@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2] btrfs: remove unused inode argument from uncompress_inline()
Date: Thu, 21 May 2015 16:45:31 +0200	[thread overview]
Message-ID: <20150521144531.GR23255@twin.jikos.cz> (raw)
In-Reply-To: <1432046805-6668-1-git-send-email-bhlee.kernel@gmail.com>

On Tue, May 19, 2015 at 11:46:45PM +0900, Byongho Lee wrote:
> The inode argument is never used from the beginning, so remove it.
> 
> Change since v1:
> - Add missing Signed-off-by line.

This ^^^ belongs ...
> 
> Signed-off-by: Byongho Lee <bhlee.kernel@gmail.com>

Reviewed-by: David Sterba <dsterba@suse.cz>

> ---

... here. The text below --- will not be part of the commit changelog,
and is meant to be read by other people.

>  fs/btrfs/inode.c | 5 ++---
>  1 file changed, 2 insertions(+), 3 deletions(-)

      reply	other threads:[~2015-05-21 14:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-19 14:46 [PATCH v2] btrfs: remove unused inode argument from uncompress_inline() Byongho Lee
2015-05-21 14:45 ` David Sterba [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=20150521144531.GR23255@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=bhlee.kernel@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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