The patch titled
drivers/char/mem.c: clean up the code
has been added to the -mm tree. Its filename is
drivers-char-memc-clean-up-the-code.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 ***
See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find
out what to do about this
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: drivers/char/mem.c: clean up the code
From: Changli Gao <xiaosuo@xxxxxxxxx>
Reduce the lines of code and simplify the logic.
Signed-off-by: Changli Gao <xiaosuo@xxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
drivers/char/mem.c | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
diff -puN drivers/char/mem.c~drivers-char-memc-clean-up-the-code drivers/char/mem.c
--- a/drivers/char/mem.c~drivers-char-memc-clean-up-the-code
+++ a/drivers/char/mem.c
@@ -47,10 +47,7 @@ static inline unsigned long size_inside_
#ifndef ARCH_HAS_VALID_PHYS_ADDR_RANGE
static inline int valid_phys_addr_range(unsigned long addr, size_t count)
{
- if (addr + count > __pa(high_memory))
- return 0;
-
- return 1;
+ return addr + count <= __pa(high_memory);
}
static inline int valid_mmap_phys_addr_range(unsigned long pfn, size_t size)
_
Patches currently in -mm which might be from xiaosuo@xxxxxxxxx are
linux-next.patch
drivers-char-memc-clean-up-the-code.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
