linux-kernel - Re: linux-next: build warnings after merge of the drivers-x86 tree

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20220324222241.42896e9e@canb.auug.org.au>
Date:   Thu, 24 Mar 2022 22:22:41 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Hans de Goede <hdegoede@...hat.com>
Cc:     Mark Gross <markgross@...nel.org>,
        "David E. Box" <david.e.box@...ux.intel.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Jonathan Corbet <corbet@....net>,
        Mauro Carvalho Chehab <mchehab@...nel.org>
Subject: Re: linux-next: build warnings after merge of the drivers-x86 tree

Hi Hans,

On Thu, 24 Mar 2022 08:39:19 +0100 Hans de Goede <hdegoede@...hat.com> wrote:
>
> I replied to your original report on March 1st, but I never got a reply
> to my reply:
> 
> """
> Thank you for the report.
> 
> So I just did:
> 
> touch Documentation/ABI/testing/sysfs-driver-intel_sdsi
> make htmldocs &> log
> 
> In a repo with drivers-x86/for-next checked out and checked the generated log files.
> But I'm not seeing these WARNINGs.
> 
> Also 'find Documentation/output/ -name "*sdsi*"' does not output anything,
> is there anything special (maybe some extra utilities?) which I need to also enable
> building of htmldocs for the files in Documentation/ABI ?
> """
> 
> If someone can let me know how to reproduce these warnings I would be happy
> to fix them.

Sorry about that.  I am just doing what you are doing but with the
whole of linux-next (which I don't think would make a difference).  One
possibility is that we are using different versions of the doco
software.

I am using Sphinx version 4.3.2 (using Python 3).

[Adding those who do doco to cc for advise]
-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped