All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aliasgar Surti <aliasgar.surti500@gmail.com>
To: dsterba@suse.cz, clm@fb.com, josef@toxicpanda.com,
	dsterba@suse.com, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2] btrfs: removed unused return variable
Date: Tue, 1 Oct 2019 12:30:08 +0530	[thread overview]
Message-ID: <20191001070008.GA9578@aliasgar> (raw)
In-Reply-To: <20190930133335.GZ2751@twin.jikos.cz>

On Mon, Sep 30, 2019 at 03:33:35PM +0200, David Sterba wrote:
> On Mon, Sep 30, 2019 at 06:30:21PM +0530, Aliasgar Surti wrote:
> > From: Aliasgar Surti <aliasgar.surti500@gmail.com>
> > 
> > Removed unused return variable and replaced it with returning
> > the value directly
> 
> This change has been sent several times and I give the same answer each
> time:
> 
> https://lore.kernel.org/linux-btrfs/20190418154913.GO20156@twin.jikos.cz/
> 
> "When switching a fuction to return void, please check the whole
> callgraph for functions that do not properly handler errors and do
> BUG_ON. You won't see errors passed from them so this gives the
> impression no error handling is needed in the caller.
> 
> This has been sent in the past, so I can point you to the 2nd paragraph
> in
> https://lore.kernel.org/linux-btrfs/20180815124425.GM24025@twin.jikos.cz/
> 
> hint: btrfs_pin_extent"

Okay, reverted back the changes and submitted v3.

Thanks,
Aliasgar

      reply	other threads:[~2019-10-01  7:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-30 13:00 [PATCH v2] btrfs: removed unused return variable Aliasgar Surti
2019-09-30 13:21 ` Nikolay Borisov
2019-09-30 13:33 ` David Sterba
2019-10-01  7:00   ` Aliasgar Surti [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=20191001070008.GA9578@aliasgar \
    --to=aliasgar.surti500@gmail.com \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=dsterba@suse.cz \
    --cc=josef@toxicpanda.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 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.