From: Anand Jain <anand.jain@oracle.com>
To: Nikolay Borisov <nborisov@suse.com>, linux-btrfs@vger.kernel.org
Cc: dsterba@suse.cz
Subject: Re: [PATCH 2/3] btrfs: cleanup btrfs_init_new_device()
Date: Tue, 26 Sep 2017 16:00:18 +0800 [thread overview]
Message-ID: <1e6f6d99-8b51-5dfe-0d5b-89a160529077@oracle.com> (raw)
In-Reply-To: <26696307-d343-e75a-5dd8-b401a8fe02d0@oracle.com>
On 09/26/2017 03:57 PM, Anand Jain wrote:
>
>> The
>> sysfs rm stands though
>
> This is a preparatory patch for 3/3, at BUG_ON it needs an exit
> without the btrfs_sysfs_add_device_link() part.
typo
s/btrfs_sysfs_add_device_link/btrfs_sysfs_rm_device_link/
> -Anand
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-09-26 7:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 12:31 [PATCH 0/3] fix bug in btrfs_init_new_device() Anand Jain
2017-09-25 12:31 ` [PATCH 1/3] btrfs: undo writable when sprouting fails Anand Jain
2017-09-25 13:03 ` Qu Wenruo
2017-09-25 14:52 ` David Sterba
2017-09-25 12:31 ` [PATCH 2/3] btrfs: cleanup btrfs_init_new_device() Anand Jain
2017-09-25 13:07 ` Nikolay Borisov
2017-09-25 13:09 ` Nikolay Borisov
2017-09-26 7:57 ` Anand Jain
2017-09-26 8:00 ` Anand Jain [this message]
2017-09-26 8:07 ` Nikolay Borisov
2017-09-26 8:45 ` Anand Jain
2017-09-25 13:08 ` Qu Wenruo
2017-09-25 14:56 ` David Sterba
2017-09-25 12:31 ` [PATCH 3/3] btrfs: fix BUG_ON in btrfs_init_new_device() Anand Jain
2017-09-26 7:48 ` [PATCH v2 0/3] fix bug " Anand Jain
2017-09-26 7:48 ` [PATCH v2 1/3] btrfs: undo writable when sprouting fails Anand Jain
2017-09-26 7:48 ` [PATCH v2 2/3] btrfs: cleanup btrfs_init_new_device() Anand Jain
2017-09-26 7:48 ` [PATCH v2 3/3] btrfs: fix BUG_ON in btrfs_init_new_device() Anand Jain
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=1e6f6d99-8b51-5dfe-0d5b-89a160529077@oracle.com \
--to=anand.jain@oracle.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@suse.com \
/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).