public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Cc: Anand Jain <anand.jain@oracle.com>
Subject: [PATCH 0/2] minor cleanups for device close and free functions
Date: Tue,  4 Apr 2023 22:55:10 +0800	[thread overview]
Message-ID: <cover.1680619177.git.anand.jain@oracle.com> (raw)

This patch series includes fixes for minor issues identified in the
btrfs_close_one_device() and btrfs_free_device() functions.

Anand Jain (2):
  btrfs: warn for any missed cleanup at btrfs_close_one_device
  btrfs: remove redundant release of alloc_state

 fs/btrfs/volumes.c | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)

-- 
2.39.2


             reply	other threads:[~2023-04-04 14:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-04 14:55 Anand Jain [this message]
2023-04-04 14:55 ` [PATCH 1/2] btrfs: warn for any missed cleanup at btrfs_close_one_device Anand Jain
2023-04-05 17:37   ` David Sterba
2023-04-06  5:15     ` Anand Jain
2023-04-04 14:55 ` [PATCH 2/2] btrfs: remove redundant release of alloc_state Anand Jain
2023-04-05 17:41 ` [PATCH 0/2] minor cleanups for device close and free functions David Sterba

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.1680619177.git.anand.jain@oracle.com \
    --to=anand.jain@oracle.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