On Thu, Jul 27, 2017 at 08:36:36PM +0300, Nikolay Borisov wrote: > Currently this function is always called with the object id of the root key of > the chunk_tree, which is always BTRFS_CHUNK_TREE_OBJECTID. So let's subsume it > straight into the function itself. No functional change. > > Signed-off-by: Nikolay Borisov <nbori...@suse.com> > --- > fs/btrfs/volumes.c | 12 +++++------- > 1 file changed, 5 insertions(+), 7 deletions(-) > > diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c > index 1c0a5fff0e2f..5a1913956f20 100644 > --- a/fs/btrfs/volumes.c > +++ b/fs/btrfs/volumes.c > @@ -1578,8 +1578,7 @@ static int btrfs_free_dev_extent(struct > btrfs_trans_handle *trans, > > static int btrfs_alloc_dev_extent(struct btrfs_trans_handle *trans, > struct btrfs_device *device, > - u64 chunk_tree, u64 chunk_offset, u64 start, > - u64 num_bytes) > + u64 chunk_offset, u64 start, u64 num_bytes)
This hunk does not apply, the context in git contains u64 chunk_objectid and I haven't found any patch that would remove or rename it. Please refresh and resend. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
