Re: [PATCH] doc/RCU/listRCU: fix an example code snippets

Ping On Wed, Jan 01, 2025 at 08:23:06AM +, Wei Yang wrote: >The example code for "Eliminating Stale Data" looks not correct: > > * rcu_read_unlock() should put after kstrdup() > * spin_unlock() should be called before return > >Signed-off-by: Wei Yang >

[PATCH] doc/RCU/listRCU: fix an example code snippets

The example code for "Eliminating Stale Data" looks not correct: * rcu_read_unlock() should put after kstrdup() * spin_unlock() should be called before return Signed-off-by: Wei Yang --- Hope my understanding is correct. --- Documentation/RCU/listRCU.rst | 3 ++- 1 file

[PATCH v2 1/2] admin-guide/memory-hotplug.rst: remove locking internal part from admin-guide

Locking Internal section exists in core-api documentation, which is more suitable for this. This patch removes the duplication part here. Signed-off-by: Wei Yang Reviewed-by: David Hildenbrand Acked-by: Mike Rapoport --- Documentation/admin-guide/mm/memory-hotplug.rst | 40

[PATCH v2 2/2] core-api/memory-hotplug.rst: divide Locking Internal section by different locks

patch divides Locking Internal section based on these two global locks to help readers to understand it. Also it adds some new finding to enrich it. [David: words arrangement] Signed-off-by: Wei Yang --- v2: adjustment based on David and Mike comment --- Documentation/core-api/memory-hotplug.rst

Re: [PATCH 2/2] core-api/memory-hotplug.rst: divide Locking Internal section by different locks

On Wed, Dec 05, 2018 at 01:13:10PM +0100, Michal Hocko wrote: >On Wed 05-12-18 10:34:26, Wei Yang wrote: >> Currently locking for memory hotplug is a little complicated. >> >> Generally speaking, we leverage the two global lock: >> >> * device_hotplug_lock

Re: [PATCH 2/2] core-api/memory-hotplug.rst: divide Locking Internal section by different locks

On Wed, Dec 05, 2018 at 10:40:45AM +0200, Mike Rapoport wrote: >On Wed, Dec 05, 2018 at 10:34:26AM +0800, Wei Yang wrote: >> Currently locking for memory hotplug is a little complicated. >> >> Generally speaking, we leverage the two global lock: >>

Re: [PATCH 2/2] core-api/memory-hotplug.rst: divide Locking Internal section by different locks

On Wed, Dec 05, 2018 at 09:08:47AM +0100, David Hildenbrand wrote: >On 05.12.18 03:34, Wei Yang wrote: >> Currently locking for memory hotplug is a little complicated. >> >> Generally speaking, we leverage the two global lock: >> >> * device_hotplug_lock

Re: [PATCH 1/2] admin-guide/memory-hotplug.rst: remove locking internal part from admin-guide

On Wed, Dec 05, 2018 at 10:30:13AM +0200, Mike Rapoport wrote: >On Wed, Dec 05, 2018 at 09:03:24AM +0100, David Hildenbrand wrote: >> On 05.12.18 03:34, Wei Yang wrote: >> > Locking Internal section exists in core-api documentation, which is more >> > suitable for

Re: [PATCH 1/2] admin-guide/memory-hotplug.rst: remove locking internal part from admin-guide

On Wed, Dec 05, 2018 at 09:03:24AM +0100, David Hildenbrand wrote: >On 05.12.18 03:34, Wei Yang wrote: >> Locking Internal section exists in core-api documentation, which is more >> suitable for this. >> >> This patch removes the duplication part here. >

[PATCH 2/2] core-api/memory-hotplug.rst: divide Locking Internal section by different locks

patch divides Locking Internal section based on these two global locks to help readers to understand it. Also it adds some new finding to enrich it. [David: words arrangement] Signed-off-by: Wei Yang --- Documentation/core-api/memory-hotplug.rst | 27 --- 1 file changed

[PATCH 1/2] admin-guide/memory-hotplug.rst: remove locking internal part from admin-guide

Locking Internal section exists in core-api documentation, which is more suitable for this. This patch removes the duplication part here. Signed-off-by: Wei Yang --- Documentation/admin-guide/mm/memory-hotplug.rst | 40 - 1 file changed, 40 deletions(-) diff --git a