lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <95c839a5-35b0-34b0-f22e-6bc45c6729b8@linux.intel.com>
Date: Wed, 30 Apr 2025 14:07:38 +0300 (EEST)
From: Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>
To: Antheas Kapenekakis <lkml@...heas.dev>
cc: Stephen Rothwell <sfr@...b.auug.org.au>, 
    Hans de Goede <hdegoede@...hat.com>, Mark Gross <markgross@...nel.org>, 
    Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, 
    Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build warning after merge of the drivers-x86 tree

On Wed, 30 Apr 2025, Antheas Kapenekakis wrote:

> On Wed, 30 Apr 2025 at 12:56, Ilpo Järvinen
> <ilpo.jarvinen@...ux.intel.com> wrote:
> >
> > On Wed, 30 Apr 2025, Antheas Kapenekakis wrote:
> >
> > > On Wed, 30 Apr 2025 at 12:45, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> > > >
> > > > Hi all,
> > > >
> > > > After merging the drivers-x86 tree, today's linux-next build (htmldocs)
> > > > produced this warning:
> > > >
> > > > Documentation/hwmon/index.rst:19: WARNING: toctree contains reference to nonexisting document 'hwmon/oxpec' [toc.not_readable]
> > > >
> > > > Introduced by commit
> > > >
> > > >   fe812896e55d ("platform/x86: oxpec: Move hwmon/oxp-sensors to platform/x86")
> > >
> > > Hm,
> > > after removing the documentation I might have left an erroneous oxcec
> > > entry in the documentation file.
> > >
> > > In some previous versions of the series the hwmon doc file was renamed
> > > but in the final one it is removed. So this file should not be introduced.
> > >
> > > Should I do a fixup commit?
> >
> > Yes please. I'll fold that into the original commit if it is easy enough
> > to do which is what I expect to be case here.
> 
> I am not at my computer with my kernel tree. I will do that later
> today if needed.
> 
> Looking at the diff:
> 
> --- a/Documentation/hwmon/index.rst
> +++ b/Documentation/hwmon/index.rst
> @@ -189,7 +189,7 @@ Hardware Monitoring Kernel Drivers
>     nzxt-kraken3
>     nzxt-smart2
>     occ
> -   oxp-sensors
> +   oxpec <-- This needs to be removed
>     pc87360
>     pc87427
>     pcf8591
> 
> If modifying the initial commit, it is probably easier for you to fix
> it now. Otherwise I will send a fixes later today (~8 hours).

It has been removed in the review-ilpo-next branch. Thanks all.

-- 
 i.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ