linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Behrens <sbehrens@giantdisaster.de>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/3] Btrfs: some cleanups around btrfs_read_fs_root_no_name()
Date: Mon, 13 May 2013 15:53:32 +0200	[thread overview]
Message-ID: <cover.1368450252.git.sbehrens@giantdisaster.de> (raw)

Just some line deletions for callers of btrfs_read_fs_root_no_name().
They repeat the check for btrfs_root_refs() after calling
btrfs_read_fs_root_no_name() and map the error to ENOENT in this case,
and btrfs_read_fs_root_no_name() already does the same for you.
send.c even checked the result for NULL which cannot happen.
And one static inline function in delayed-inode.c that called
btrfs_read_fs_root_no_name() was not at all used anymore.

Stefan Behrens (3):
  Btrfs: delete unused function
  Btrfs: cleanup, btrfs_read_fs_root_no_name() doesn't return NULL
  Btrfs: cleanup: don't check the same thing twice

 fs/btrfs/delayed-inode.c | 14 --------------
 fs/btrfs/export.c        |  5 -----
 fs/btrfs/file.c          |  4 ----
 fs/btrfs/inode.c         | 10 ----------
 fs/btrfs/ioctl.c         |  5 -----
 fs/btrfs/send.c          |  8 ++------
 fs/btrfs/super.c         |  3 ---
 7 files changed, 2 insertions(+), 47 deletions(-)

-- 
1.8.2.2


             reply	other threads:[~2013-05-13 13:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-13 13:53 Stefan Behrens [this message]
2013-05-13 13:53 ` [PATCH 1/3] Btrfs: delete unused function Stefan Behrens
2013-05-13 13:53 ` [PATCH 2/3] Btrfs: cleanup, btrfs_read_fs_root_no_name() doesn't return NULL Stefan Behrens
2013-05-13 13:53 ` [PATCH 3/3] Btrfs: cleanup: don't check the same thing twice Stefan Behrens

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=cover.1368450252.git.sbehrens@giantdisaster.de \
    --to=sbehrens@giantdisaster.de \
    --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;
as well as URLs for NNTP newsgroup(s).