From: Bagas Sanjaya <bagasdotme@gmail.com>
To: dri-devel@lists.freedesktop.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, oe-kbuild-all@lists.linux.dev
Cc: "David Airlie" <airlied@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Jonathan Corbet" <corbet@lwn.net>,
"Maíra Canal" <mcanal@igalia.com>,
"Bagas Sanjaya" <bagasdotme@gmail.com>,
"kernel test robot" <lkp@intel.com>
Subject: [PATCH] Documentation: gpu: vc4: add blank line separator before KUnit code block
Date: Sun, 11 Dec 2022 12:30:52 +0700 [thread overview]
Message-ID: <20221211053051.18125-1-bagasdotme@gmail.com> (raw)
In-Reply-To: <202212102116.A10vg3jG-lkp@intel.com>
kernel test robot reports htmldocs warning:
Documentation/gpu/vc4.rst:65: WARNING: Unexpected indentation.
The warning is due to missing blank line separator between KUnit mock
driver sentence and its code block.
Add the separator to fix the warning.
Link: https://lore.kernel.org/linux-doc/202212102116.A10vg3jG-lkp@intel.com/
Fixes: 5304c8e6010012 ("Documentation: gpu: vc4: Add KUnit Tests Section")
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
Documentation/gpu/vc4.rst | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/gpu/vc4.rst b/Documentation/gpu/vc4.rst
index a2375f1584e6d9..ec920c4f5bb322 100644
--- a/Documentation/gpu/vc4.rst
+++ b/Documentation/gpu/vc4.rst
@@ -62,6 +62,7 @@ integration tests.
These tests are using a mock driver and can be ran using the
command::
+
./tools/testing/kunit/kunit.py run \
--kunitconfig=drivers/gpu/drm/vc4/tests/.kunitconfig \
--cross_compile aarch64-linux-gnu- --arch arm64
base-commit: 612e241fb4bcd98d8ff9da7a795abb86b8ccfe38
--
An old man doll... just what I always wanted! - Clara
next parent reply other threads:[~2022-12-11 5:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202212102116.A10vg3jG-lkp@intel.com>
2022-12-11 5:30 ` Bagas Sanjaya [this message]
2022-12-11 11:32 ` Maíra Canal
2022-12-11 12:44 ` Bagas Sanjaya
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=20221211053051.18125-1-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=airlied@gmail.com \
--cc=corbet@lwn.net \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mcanal@igalia.com \
--cc=mripard@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tzimmermann@suse.de \
/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
all inboxes | Powered by JetHome®