From: Jonathan Corbet <corbet@lwn.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the jc_docs tree
Date: Wed, 12 Feb 2025 08:09:22 -0700 [thread overview]
Message-ID: <871pw3urml.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250212155253.5bf0513a@canb.auug.org.au>
Stephen Rothwell <sfr@canb.auug.org.au> writes:
> Hi all,
>
> After merging the jc_docs tree, today's linux-next build (htmldocs)
> produced these warnings:
>
> WARNING: /sys/devices/system/cpu/cpuX/topology/physical_package_id is defined 2 times: Documentation/ABI/stable/sysfs-devices-system-cpu:27; Documentation/ABI/testing/sysfs-devices-system-cpu:70
> WARNING: /sys/devices/system/cpu/cpuX/topology/ppin is defined 2 times: Documentation/ABI/stable/sysfs-devices-system-cpu:89; Documentation/ABI/testing/sysfs-devices-system-cpu:70
>
> I am not sure what introduced these warnings, but I am guessing Mauro's
> changes have exposed them - the two Documentation files above have not
> changed since my last build.
Exactly - the situation has been there for who knows how long, it's just
that we're hearing about it now.
Thanks,
jon
next prev parent reply other threads:[~2025-02-12 15:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 4:52 linux-next: build warnings after merge of the jc_docs tree Stephen Rothwell
2025-02-12 15:09 ` Jonathan Corbet [this message]
2025-02-12 21:05 ` Mauro Carvalho Chehab
-- strict thread matches above, loose matches on Subject: below --
2022-10-31 6:05 Stephen Rothwell
2022-10-31 9:02 ` Bagas Sanjaya
2022-10-31 14:27 ` Jonathan Corbet
2022-01-27 3:15 Stephen Rothwell
2022-01-27 3:36 ` Stephen Rothwell
2022-01-27 18:22 ` Jonathan Corbet
2021-03-26 7:54 Stephen Rothwell
2021-03-26 19:20 ` Jonathan Corbet
2021-03-10 3:20 Stephen Rothwell
2021-01-19 6:13 Stephen Rothwell
2021-01-19 6:45 ` Stephen Rothwell
2021-01-19 7:16 ` Stephen Rothwell
2021-01-19 9:07 ` Mauro Carvalho Chehab
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=871pw3urml.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=sfr@canb.auug.org.au \
/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