[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <57392381-497c-49d8-9ad7-4b50c4939448@lunn.ch>
Date: Fri, 24 Jan 2025 17:15:10 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Breno Leitao <leitao@...ian.org>
Cc: Andrew Lunn <andrew+netdev@...n.ch>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Simon Horman <horms@...nel.org>, Jonathan Corbet <corbet@....net>,
Shuah Khan <shuah@...nel.org>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kselftest@...r.kernel.org, rdunlap@...radead.org,
kernel-team@...a.com
Subject: Re: [PATCH RFC net-next v3 8/8] netconsole: docs: Add documentation
for CPU number auto-population
> +CPU number auto population in userdata
> +--------------------------------------
> +
> +Inside the netconsole configfs hierarchy, there is a file called
> +`cpu_nr` under the `userdata` directory. This file is used to enable or disable
> +the automatic CPU number population feature. This feature automatically
> +populates the CPU number that is sending the message.
Biking shedding a bit, but to me `cpu_nr` is the number of a
CPU. However, you want this to be an enable/disable feature. Would
`cpu_nr_enable`, or `cpu_nr_auto_populate` be clearer?
Andrew
Powered by blists - more mailing lists