Re: [PATCH 2/5] Documentation: admin-guide: fix trailing whitespace in cgroup-v2.rst
Randy Dunlap <[email protected]>
| Newsgroups | org.kernel.vger.cgroups,org.kernel.vger.linux-doc,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <[email protected]> |
On 7/18/26 9:14 AM, Weijie Yuan wrote: > On Sat, Jul 18, 2026 at 04:19:08PM +0100, Yahya Toubali wrote: >> Remove trailing spaces on lines 1335 and 2197. >> >> Signed-off-by: Yahya Toubali <[email protected]> > > Hmmm, for a file that might be modified, I wonder if it makes sense to > include fixed line numbers in the commit message. i.e. When the line > number changes, your commit message will become meaningless. > > I'd love to hear others' comments. I wouldn't include the line numbers... >> --- >> Documentation/admin-guide/cgroup-v2.rst | 5 +++-- >> 1 file changed, 3 insertions(+), 2 deletions(-) >> >> diff --git a/Documentation/admin-guide/cgroup-v2.rst b/Documentation/admin-guide/cgroup-v2.rst >> index 14b8c571c0d1..f15a613fed6a 100644 >> --- a/Documentation/admin-guide/cgroup-v2.rst >> +++ b/Documentation/admin-guide/cgroup-v2.rst >> @@ -1,4 +1,5 @@ >> .. _cgroup-v2: >> +.. SPDX-License-Identifier: GPL-2.0 >> >> ================ >> Control Group v2 >> @@ -1332,7 +1333,7 @@ PAGE_SIZE multiple when read back. >> cgroup is within its effective low boundary, the cgroup's >> memory won't be reclaimed unless there is no reclaimable >> memory available in unprotected cgroups. >> - Above the effective low boundary (or >> + Above the effective low boundary (or >> effective min boundary if it is higher), pages are reclaimed >> proportionally to the overage, reducing reclaim pressure for >> smaller overages. >> @@ -2194,7 +2195,7 @@ of the two is enforced. >> >> cgroup writeback requires explicit support from the underlying >> filesystem. Currently, cgroup writeback is implemented on ext2, ext4, >> -btrfs, f2fs, and xfs. On other filesystems, all writeback IOs are >> +btrfs, f2fs, and xfs. On other filesystems, all writeback IOs are >> attributed to the root cgroup. >> >> There are inherent differences in memory and writeback management > -- ~Randy