From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-kernel@vger.kernel.org,
Michael Ellerman <mpe@ellerman.id.au>,
"Nysal Jan K.A" <nysal@linux.ibm.com>,
"Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>,
Baoquan He <bhe@redhat.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
James Morse <james.morse@arm.com>,
Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
Sourabh Jain <sourabhjain@linux.ibm.com>
Subject: Re: [PATCH] docs: ABI: drop two duplicate symbols
Date: Thu, 13 Feb 2025 19:21:35 +0700 [thread overview]
Message-ID: <Z63jz7uEoMNeaIga@archie.me> (raw)
In-Reply-To: <c3dce809f577584cf9aedafc6c2a0d5a9ca909ac.1739394480.git.mchehab+huawei@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 2687 bytes --]
On Wed, Feb 12, 2025 at 10:08:01PM +0100, Mauro Carvalho Chehab wrote:
> As warned by get_abi.py, there are two symbols that are
> defined twice:
>
> WARNING: /sys/devices/system/cpu/cpuX/topology/physical_package_id is defined 2 times: \
> /new_devel/v4l/docs/Documentation/ABI/stable/sysfs-devices-system-cpu:27; \
> /new_devel/v4l/docs/Documentation/ABI/testing/sysfs-devices-system-cpu:70
> WARNING: /sys/devices/system/cpu/cpuX/topology/ppin is defined 2 times: \
> /new_devel/v4l/docs/Documentation/ABI/stable/sysfs-devices-system-cpu:89; \
> /new_devel/v4l/docs/Documentation/ABI/testing/sysfs-devices-system-cpu:70
>
> As the documentation at testing/sysfs-devices-system-cpu, drop
> the duplicated one from stable.
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> ---
> Documentation/ABI/stable/sysfs-devices-system-cpu | 10 ----------
> 1 file changed, 10 deletions(-)
>
> diff --git a/Documentation/ABI/stable/sysfs-devices-system-cpu b/Documentation/ABI/stable/sysfs-devices-system-cpu
> index 902392d7eddf..cf78bd99f6c8 100644
> --- a/Documentation/ABI/stable/sysfs-devices-system-cpu
> +++ b/Documentation/ABI/stable/sysfs-devices-system-cpu
> @@ -24,12 +24,6 @@ Description: Default value for the Data Stream Control Register (DSCR) on
> If set by a process it will be inherited by child processes.
> Values: 64 bit unsigned integer (bit field)
>
> -What: /sys/devices/system/cpu/cpuX/topology/physical_package_id
> -Description: physical package id of cpuX. Typically corresponds to a physical
> - socket number, but the actual value is architecture and platform
> - dependent.
> -Values: integer
> -
> What: /sys/devices/system/cpu/cpuX/topology/die_id
> Description: the CPU die ID of cpuX. Typically it is the hardware platform's
> identifier (rather than the kernel's). The actual value is
> @@ -86,10 +80,6 @@ What: /sys/devices/system/cpu/cpuX/topology/die_cpus
> Description: internal kernel map of CPUs within the same die.
> Values: hexadecimal bitmask.
>
> -What: /sys/devices/system/cpu/cpuX/topology/ppin
> -Description: per-socket protected processor inventory number
> -Values: hexadecimal.
> -
> What: /sys/devices/system/cpu/cpuX/topology/die_cpus_list
> Description: human-readable list of CPUs within the same die.
> The format is like 0-3, 8-11, 14,17.
The warnings squashed away, thanks!
Tested-by: Bagas Sanjaya <bagasdotme@gmail.com>
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-02-13 12:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 21:08 Mauro Carvalho Chehab
2025-02-13 12:21 ` Bagas Sanjaya [this message]
2025-02-13 16:24 ` Jonathan Corbet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Z63jz7uEoMNeaIga@archie.me \
--to=bagasdotme@gmail.com \
--cc=bhe@redhat.com \
--cc=corbet@lwn.net \
--cc=james.morse@arm.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=nysal@linux.ibm.com \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=sfr@canb.auug.org.au \
--cc=sourabhjain@linux.ibm.com \
--cc=thomas.lendacky@amd.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®