The patch titled
Subject: mm/page_owner.c: use PTR_ERR_OR_ZERO()
has been added to the -mm tree. Its filename is
mm-page_owner-use-ptr_err_or_zero.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/mm-page_owner-use-ptr_err_or_zero.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/mm-page_owner-use-ptr_err_or_zero.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Vasyl Gomonovych <gomonovych@xxxxxxxxx>
Subject: mm/page_owner.c: use PTR_ERR_OR_ZERO()
Fix ptr_ret.cocci warnings:
mm/page_owner.c:639:1-3: WARNING: PTR_ERR_OR_ZERO can be used
Use PTR_ERR_OR_ZERO rather than if(IS_ERR(...)) + PTR_ERR
Generated by: scripts/coccinelle/api/ptr_ret.cocci
Link: http://lkml.kernel.org/r/1511824101-9597-1-git-send-email-gomonovych@xxxxxxxxx
Signed-off-by: Vasyl Gomonovych <gomonovych@xxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
mm/page_owner.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff -puN mm/page_owner.c~mm-page_owner-use-ptr_err_or_zero mm/page_owner.c
--- a/mm/page_owner.c~mm-page_owner-use-ptr_err_or_zero
+++ a/mm/page_owner.c
@@ -636,9 +636,7 @@ static int __init pageowner_init(void)
dentry = debugfs_create_file("page_owner", S_IRUSR, NULL,
NULL, &proc_page_owner_operations);
- if (IS_ERR(dentry))
- return PTR_ERR(dentry);
- return 0;
+ return PTR_ERR_OR_ZERO(dentry);
}
late_initcall(pageowner_init)
_
Patches currently in -mm which might be from gomonovych@xxxxxxxxx are
mm-page_owner-use-ptr_err_or_zero.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
