public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Jonathan Cameron <Jonathan.Cameron@Huawei•com>
Cc: Trevor Gamblin <tgamblin@baylibre•com>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: build warning after merge of the iio tree
Date: Tue, 15 Oct 2024 15:50:21 +1100	[thread overview]
Message-ID: <20241015155021.6707d315@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 299 bytes --]

Hi all,

After merging the iio tree, today's linux-next build (htmldocs) produced
this warning:

Documentation/iio/ad7625.rst: WARNING: document isn't included in any toctree

Introduced by commit

  b4a35432dbd0 ("docs: iio: new docs for ad7625 driver")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2024-10-15  4:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-15  4:50 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-08-18  2:41 linux-next: build warning after merge of the iio tree Stephen Rothwell
2025-04-15  6:28 Stephen Rothwell
2025-04-15  7:35 ` Angelo Dureghello
2024-11-07 11:40 Stephen Rothwell
2024-11-07 12:25 ` Jonathan Cameron
2024-10-29  4:50 Stephen Rothwell
2024-10-29  9:43 ` Jonathan Cameron
2024-08-20  3:47 Stephen Rothwell
2024-08-20  9:08 ` Jonathan Cameron
2024-06-05  3:34 Stephen Rothwell
2024-02-28  3:51 Stephen Rothwell
2022-07-01  5:29 Stephen Rothwell
2022-07-01  8:28 ` Stephen Rothwell
2022-07-01  9:28   ` Jonathan Cameron
2022-07-01 10:43   ` Jonathan Cameron
2022-04-28  7:37 Stephen Rothwell
2022-04-28  8:07 ` Miquel Raynal
2022-02-11  7:42 Stephen Rothwell

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=20241015155021.6707d315@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=Jonathan.Cameron@Huawei$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=tgamblin@baylibre$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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