From: Takashi Iwai <tiwai@suse.de>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Linux ALSA Subsystem Development <alsa-devel@alsa-project.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Takashi Iwai <tiwai@suse.com>, Jonathan Corbet <corbet@lwn.net>,
Oswald Buddenhagen <oswald.buddenhagen@gmx.de>,
Miquel Raynal <miquel.raynal@bootlin.com>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] ALSA: docs: Fix code block indentation in ALSA driver example
Date: Wed, 03 May 2023 08:09:01 +0200 [thread overview]
Message-ID: <87fs8endz6.wl-tiwai@suse.de> (raw)
In-Reply-To: <20230503035416.62722-1-bagasdotme@gmail.com>
On Wed, 03 May 2023 05:54:16 +0200,
Bagas Sanjaya wrote:
>
> Sphinx reports htmldocs warnings:
>
> Documentation/sound/kernel-api/writing-an-alsa-driver.rst:3997: WARNING: Literal block expected; none found.
> Documentation/sound/kernel-api/writing-an-alsa-driver.rst:4004: WARNING: Literal block expected; none found.
> Documentation/sound/kernel-api/writing-an-alsa-driver.rst:4009: WARNING: Unexpected indentation.
> Documentation/sound/kernel-api/writing-an-alsa-driver.rst:4035: WARNING: Literal block expected; none found.
>
> These are due to indentation of example driver snippets which is outside
> the code block scope.
>
> Fix these by indenting code blocks in question to the scope.
>
> Fixes: 4d421eebe1465d ("ALSA: docs: writing-an-alsa-driver.rst: polishing")
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/linux-doc/202305021822.4U6XOvGf-lkp@intel.com/
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
Thanks, applied.
Takashi
prev parent reply other threads:[~2023-05-03 6:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 3:54 [PATCH] ALSA: docs: Fix code block indentation in ALSA driver example Bagas Sanjaya
2023-05-03 6:09 ` Takashi Iwai [this message]
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=87fs8endz6.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=miquel.raynal@bootlin.com \
--cc=oswald.buddenhagen@gmx.de \
--cc=tiwai@suse.com \
/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