[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aEG8fLzv7M_mo71_@localhost.localdomain>
Date: Thu, 5 Jun 2025 17:49:16 +0200
From: Oscar Salvador <osalvador@...e.de>
To: David Hildenbrand <david@...hat.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Vlastimil Babka <vbabka@...e.cz>,
Jonathan Cameron <Jonathan.Cameron@...wei.com>,
Harry Yoo <harry.yoo@...cle.com>, Rakie Kim <rakie.kim@...com>,
Hyeonggon Yoo <42.hyeyoo@...il.com>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5 02/10] mm,memory_hotplug: Remove
status_change_nid_normal and update documentation
On Thu, Jun 05, 2025 at 04:54:00PM +0200, David Hildenbrand wrote:
> On 05.06.25 16:22, Oscar Salvador wrote:
> > Now that the last user of status_change_nid_normal is gone, we can remove it.
> > Update documentation accordingly.
> >
> > Signed-off-by: Oscar Salvador <osalvador@...e.de>
> > ---
> > Documentation/core-api/memory-hotplug.rst | 3 ---
> > .../translations/zh_CN/core-api/memory-hotplug.rst | 3 ---
>
> I'm running into similar issues with CN-only doc, which I will happily let
> bitrot, because I will not learn a new language just so I can update
> documentation.
>
> ... I raised in the past that having CN doc in the tree is absurdly stupid.
>
> In your case, likely removing the doc works.
Yeah, git send-mail wasn't happy about this one and screamed something
about encoding.
I was this close to completely disregard CN Docs, but since it was only
removing stuff, I went "meh, ok". :-)
I'm not entirely sure how uptodated are those though, not only for
memory-hotplug but for other parts of the kernel.
--
Oscar Salvador
SUSE Labs
Powered by blists - more mailing lists