All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikolay Borisov <nborisov@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: Nikolay Borisov <nborisov@suse.com>
Subject: [PATCH 0/3] Cleanup backref_in_log and its callers
Date: Fri, 30 Aug 2019 17:44:46 +0300	[thread overview]
Message-ID: <20190830144449.23882-1-nborisov@suse.com> (raw)

This series cleans up backref_in_log and its callers. Patch 1 removes the 
opencoding of btrfs_find_name_in_backref which greatly simplifies backref_in_log
itself. 

Patch 2 properly propagates error values of the internal functions to
backref_in_log's callers and also fixes, where necessary, callers to cope with 
those ret values. 

Patch 3 continues in the spirit of the previous patch, in that it open codes 
name_in_log_ref so that the caller can properly handle backref_in_log retvals. 

Nikolay Borisov (3):
  btrfs: Don't opencode btrfs_find_name_in_backref in backref_in_log
  btrfs: Properly handle backref_in_log retval
  btrfs: Open-code name_in_log_ref in replay_one_name

 fs/btrfs/tree-log.c | 113 +++++++++++++++++---------------------------
 1 file changed, 44 insertions(+), 69 deletions(-)

-- 
2.17.1


             reply	other threads:[~2019-08-30 14:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-30 14:44 Nikolay Borisov [this message]
2019-08-30 14:44 ` [PATCH 1/3] btrfs: Don't opencode btrfs_find_name_in_backref in backref_in_log Nikolay Borisov
2019-09-24 17:09   ` David Sterba
2019-08-30 14:44 ` [PATCH 2/3] btrfs: Properly handle backref_in_log retval Nikolay Borisov
2019-09-24 17:09   ` David Sterba
2019-09-25 11:03     ` [PATCH v2] " Nikolay Borisov
2019-09-26  9:31       ` Filipe Manana
2019-09-26 10:39         ` Nikolay Borisov
2019-10-03 12:55           ` David Sterba
2019-10-03 13:07             ` David Sterba
2019-08-30 14:44 ` [PATCH 3/3] btrfs: Open-code name_in_log_ref in replay_one_name Nikolay Borisov

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=20190830144449.23882-1-nborisov@suse.com \
    --to=nborisov@suse.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.