redonkable/remarkable-linux
redonkable/remarkable-linux
1
0
Fork 0
Code Releases Activity

pnfs/blocklayout: remove some debugging

Browse source 
The kbuild test robot complained that we got the printk format wrong.
Let's just kill these printks instead of fixing them as there is not
point after the initial tree algorithm debugging.

Reported-by: kbuild test robot <fengguang.wu@intel.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
This commit is contained in:
Christoph Hellwig 2014-09-10 17:36:28 -07:00 committed by Trond Myklebust
parent 8d11620e1e
commit 3e3f6b4e26
1 changed files with 0 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
fs/nfs/blocklayout/extent_tree.c
View file

@ -370,9 +370,6 @@ ext_tree_split(struct rb_root *root, struct pnfs_block_extent *be,
struct pnfs_block_extent *new;
sector_t orig_len = be->be_length;
dprintk("%s: need split for 0x%lx:0x%lx at 0x%lx\n",
__func__, be->be_f_offset, ext_f_end(be), split);
new = kzalloc(sizeof(*new), GFP_ATOMIC);
if (!new)
return -ENOMEM;
@ -387,11 +384,6 @@ ext_tree_split(struct rb_root *root, struct pnfs_block_extent *be,
new->be_tag = be->be_tag;
new->be_device = nfs4_get_deviceid(be->be_device);
dprintk("%s: got 0x%lx:0x%lx!\n",
__func__, be->be_f_offset, ext_f_end(be));
dprintk("%s: got 0x%lx:0x%lx!\n",
__func__, new->be_f_offset, ext_f_end(new));
__ext_tree_insert(root, new, false);
return 0;
}