All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the sound tree
Date: Mon, 23 Aug 2021 16:27:20 +0200	[thread overview]
Message-ID: <s5h4kbg44on.wl-tiwai@suse.de> (raw)
In-Reply-To: <20210823200002.45fbc553@canb.auug.org.au>

On Mon, 23 Aug 2021 12:00:02 +0200,
Stephen Rothwell wrote:
> 
> Hi all,
> 
> After merging the sound tree, today's linux-next build (htmldocs)
> produced this warning:
> 
> Documentation/sound/alsa-configuration.rst:2258: WARNING: Unexpected indentation.
> 
> Introduced by commit
> 
>   a39978ed6df1 ("ALSA: doc: Add the description of quirk_flags option for snd-usb-audio")

Thanks for the report, now the fix was queued:
  https://lore.kernel.org/r/20210823113518.30134-1-tiwai@suse.de


Takashi

  reply	other threads:[~2021-08-23 14:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-23 10:00 linux-next: build warning after merge of the sound tree Stephen Rothwell
2021-08-23 14:27 ` Takashi Iwai [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-07-15  7:04 Stephen Rothwell
2024-09-02  3:29 Stephen Rothwell
2024-09-02  6:22 ` Takashi Iwai
2024-09-02  6:49 ` Stephen Rothwell
2024-09-02  6:54   ` Stephen Rothwell
2023-08-25  5:29 Stephen Rothwell
2023-08-25  9:24 ` Takashi Iwai
2023-02-08 23:48 Stephen Rothwell
2023-02-09  3:14 ` Stephen Rothwell
2020-05-01  4:03 Stephen Rothwell
2020-05-01  7:33 ` Takashi Iwai
2019-12-12  0:28 Stephen Rothwell
2019-01-21  0:21 Stephen Rothwell
2019-01-21  8:13 ` Takashi Iwai
2010-03-30  3:48 Stephen Rothwell
2010-03-30  6:07 ` Takashi Iwai
2010-02-23  5:07 Stephen Rothwell
2010-02-23  5:20 ` Luke Yelavich
2010-02-23  7:11   ` Takashi Iwai

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=s5h4kbg44on.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.