On 5/22/23 22:56, Andrew Morton wrote: > The patch titled > Subject: mm/mlock: rename mlock_future_check() to mlock_future_ok() > has been added to the -mm mm-unstable branch. Its filename is > mm-mlock-rename-mlock_future_check-to-mlock_future_ok.patch > > This patch will shortly appear at > https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/mm-mlock-rename-mlock_future_check-to-mlock_future_ok.patch > > This patch will later appear in the mm-unstable branch at > git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm > > 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/process/submit-checklist.rst when testing your code *** > > The -mm tree is included into linux-next via the mm-everything > branch at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm > and is updated there every 2-3 working days > > ------------------------------------------------------ > From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> > Subject: mm/mlock: rename mlock_future_check() to mlock_future_ok() > Date: Mon May 22 01:52:10 PM PDT 2023 > > It is felt that the name mlock_future_check() is vague - it doesn't > particularly convey the function's operation. mlock_future_ok() is a > clearer name for a predicate function. > > Cc: Liam Howlett <liam.howlett@xxxxxxxxxx> > Cc: Lorenzo Stoakes <lstoakes@xxxxxxxxx> > Cc: Mike Rapoport (IBM) <rppt@xxxxxxxxxx> > Cc: Vlastimil Babka <vbabka@xxxxxxx> > Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> Acked-by: Vlastimil Babka <vbabka@xxxxxxx>
