RFC follow up nodereclaim for 32b fix
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest2 patches 9 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | mm, vmscan: consider eligible zones in get_scan_countmm/ | +28 | 14 replies | |
| 2/2 | mm, vmscan: cleanup inactive_list_is_lowmm/ | +10 | 3 replies |
Reviews trailers per patch
All 2 patches have a Reviewed-by or Acked-by.
| Patch | Minchan Kim | Hillf Danton | Johannes Weiner |
|---|---|---|---|
| 1/2 | A-b A-b A-b A-b | A-b A-b A-b A-b | A-b |
| 2/2 | A-b | A-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes. Scroll the table sideways for all 3 reviewers.
Cover letter [RFC PATCH 0/2] follow up nodereclaim for 32b fix
Hi,
this is a follow up fix on top of [1]. I wasn't able to trigger bad things happening without the patch but the fix should be quite obvious and should make sense in general. I am sending this as an RFC, though, because g_u_p is better to not touch without strong reasons because it is just too easy to screw up.
The second patch is just a cleanup on top.
[1] http://lkml.kernel.org/r/[email protected]
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>