From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Simona Vetter <simona.vetter@ffwll.ch>,
Jani Nikula <jani.nikula@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: Imre Deak <imre.deak@intel.com>,
Intel Graphics <intel-gfx@lists.freedesktop.org>,
DRI <dri-devel@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warnings after merge of the drm-intel tree
Date: Wed, 12 Mar 2025 23:25:06 +1100 [thread overview]
Message-ID: <20250312232506.47451f83@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 542 bytes --]
Hi all,
After merging the drm-intel tree, today's linux-next build (htmldocs)
produced these warnings:
Documentation/gpu/i915:141: drivers/gpu/drm/i915/display/intel_hotplug.c:1068: ERROR: Unexpected indentation. [docutils]
Documentation/gpu/i915:141: drivers/gpu/drm/i915/display/intel_hotplug.c:1069: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils]
Introduced by commit
0d77a3e0ea90 ("drm/i915/hpd: Add support for blocking the IRQ handling on an HPD pin")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-03-12 12:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 12:25 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-05 3:16 linux-next: build warnings after merge of the drm-intel tree Stephen Rothwell
2024-04-05 6:59 ` Golani, Mitulkumar Ajitkumar
2023-01-05 3:27 Stephen Rothwell
2019-01-07 23:50 Stephen Rothwell
2016-10-18 23:57 Stephen Rothwell
2016-10-19 1:57 ` Zhenyu Wang
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=20250312232506.47451f83@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=dri-devel@lists.freedesktop.org \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=simona.vetter@ffwll.ch \
/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