From: Anand Jain <anand.jain@oracle.com>
To: dsterba@suse.cz, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: add helper for device path or missing
Date: Tue, 5 Dec 2017 09:19:04 +0800 [thread overview]
Message-ID: <3dee80c1-2208-81ef-f315-dfa6e7e6d6cf@oracle.com> (raw)
In-Reply-To: <20171204193116.GA3553@twin.jikos.cz>
On 12/05/2017 03:31 AM, David Sterba wrote:
> On Tue, Nov 28, 2017 at 10:43:10AM +0800, Anand Jain wrote:
>> This patch creates a helper function to get either the rcu device path
>> or missing.
>>
>> Signed-off-by: Anand Jain <anand.jain@oracle.com>
>> ---
>> fs/btrfs/dev-replace.c | 22 +++++++++++-----------
>> 1 file changed, 11 insertions(+), 11 deletions(-)
>>
>> diff --git a/fs/btrfs/dev-replace.c b/fs/btrfs/dev-replace.c
>> index 7c655f9a7a50..4b6ceb38cb5f 100644
>> --- a/fs/btrfs/dev-replace.c
>> +++ b/fs/btrfs/dev-replace.c
>> @@ -304,6 +304,11 @@ void btrfs_after_dev_replace_commit(struct btrfs_fs_info *fs_info)
>> dev_replace->cursor_left_last_write_of_item;
>> }
>>
>> +static inline char *dev_missing_or_rcu_str(struct btrfs_device *device)
>> +{
>> + return device->missing ? "<missing disk>" : rcu_str_deref(device->name);
>> +}
>
> I'd change it to dev_name, as long as it stays a local helper in
> dev-replace. I'm now merging the dev_state patches which depend on this
> patch so I'll rename it myself so you don't have to refresh and resend
> the patches.
I am not good at naming, thanks for fixing David.
- 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
>
prev parent reply other threads:[~2017-12-05 1:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 2:43 [PATCH] btrfs: add helper for device path or missing Anand Jain
2017-12-04 19:31 ` David Sterba
2017-12-05 1:19 ` Anand Jain [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=3dee80c1-2208-81ef-f315-dfa6e7e6d6cf@oracle.com \
--to=anand.jain@oracle.com \
--cc=dsterba@suse.cz \
--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).