From aa910f1628d4adcfa967d4ef09bc2e82e6bbba89 Mon Sep 17 00:00:00 2001 From: Bruno Haible Date: Sat, 22 Jun 2024 13:05:11 +0200 Subject: [PATCH] physmem: Fix typo. * lib/physmem.h (physmem_claimable): Fix typo in comment. --- ChangeLog | 5 +++++ lib/physmem.h | 2 +- 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/ChangeLog b/ChangeLog index f81ae03de7..8d28459959 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +2024-06-22 Bruno Haible + + physmem: Fix typo. + * lib/physmem.h (physmem_claimable): Fix typo in comment. + 2024-06-22 Bruno Haible c-xvasprintf: Guarantee a non-NULL result. diff --git a/lib/physmem.h b/lib/physmem.h index 542dbf214c..9c5438d016 100644 --- a/lib/physmem.h +++ b/lib/physmem.h @@ -39,7 +39,7 @@ double physmem_available (void); aggressivity. For AGGRESSIVITY == 0.0, the result is like physmem_available (): the amount of memory the application can use without hindering any other process. - For AGGRESSIVITY == 1,0, the result is the amount of memory the application + For AGGRESSIVITY == 1.0, the result is the amount of memory the application can use, while causing memory shortage to other processes, but without bringing the machine into an out-of-memory state. Values in between, for example AGGRESSIVITY == 0.5, are a reasonable middle -- 2.39.5