From: Johannes Thumshirn <jthumshirn@suse.de>
To: Nikolay Borisov <nborisov@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 1/4] btrfs: Rename found_type to extent_type
Date: Mon, 17 Dec 2018 09:54:20 +0100 [thread overview]
Message-ID: <96db5600-a7f6-d3b5-32c3-e36e170e439f@suse.de> (raw)
In-Reply-To: <20181217083602.10166-2-nborisov@suse.com>
Looks good,
Reviewed-by: Johannes Thumshirn <jthumshirn@suse.de>
--
Johannes Thumshirn SUSE Labs Filesystems
jthumshirn@suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
next prev parent reply other threads:[~2018-12-17 8:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 8:35 [PATCH 0/4] Misc cleanups of btrfs_get_extent Nikolay Borisov
2018-12-17 8:35 ` [PATCH 1/4] btrfs: Rename found_type to extent_type Nikolay Borisov
2018-12-17 8:54 ` Johannes Thumshirn [this message]
2018-12-17 9:05 ` Qu Wenruo
2018-12-17 8:36 ` [PATCH 2/4] btrfs: Consolidate retval checking of core btree functions Nikolay Borisov
2018-12-17 8:55 ` Johannes Thumshirn
2018-12-17 8:57 ` Nikolay Borisov
2018-12-17 9:09 ` Qu Wenruo
2018-12-17 9:23 ` Nikolay Borisov
2018-12-17 9:49 ` [PATCH v2 " Nikolay Borisov
2018-12-17 11:00 ` Qu Wenruo
2018-12-17 8:36 ` [PATCH 3/4] btrfs: Refactor retval handling of btrfs_lookup_file_extent in btrfs_get_extent Nikolay Borisov
2018-12-17 9:07 ` Johannes Thumshirn
2019-01-02 17:05 ` David Sterba
2019-01-02 17:43 ` Nikolay Borisov
2019-01-07 15:22 ` Johannes Thumshirn
2019-01-07 18:46 ` David Sterba
2019-01-08 7:43 ` Nikolay Borisov
2018-12-17 8:36 ` [PATCH 4/4] btrfs: Remove not_found_em label from btrfs_get_extent Nikolay Borisov
2018-12-17 9:08 ` Johannes Thumshirn
2019-01-02 17:08 ` [PATCH 0/4] Misc cleanups of btrfs_get_extent 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=96db5600-a7f6-d3b5-32c3-e36e170e439f@suse.de \
--to=jthumshirn@suse.de \
--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).