From: Takashi Iwai <tiwai@suse.de>
To: "Mauro Carvalho Chehab" <mchehab+samsung@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
dri-devel@lists.freedesktop.org, Jaroslav Kysela <perex@perex.cz>,
Eric Paris <eparis@parisplace.org>,
linux-clk@vger.kernel.org, James Morris <jmorris@namei.org>,
Alan Stern <stern@rowland.harvard.edu>,
xen-devel@lists.xenproject.org, Boqun Feng <boqun.feng@gmail.com>,
Nicholas Piggin <npiggin@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Antoine Jacquet <royale@zerezo.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Li Zefan <lizefan@huawei.com>,
linux-crypto@vger.kernel.org, Mark Rutland <mark.rutland@arm.com>,
alsa-devel@alsa-project.org,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
David Airlie <airlied@linux.ie>,
Max Filippov <jcmvbkbc@gmail.com>,
Harry Wei <harryxiyou@gmail.com>,
selinux@tycho.nsa.gov, Paul Moore
Subject: Re: [PATCH v2 09/11] docs: Fix some broken references
Date: Sun, 13 May 2018 09:13:18 +0200 [thread overview]
Message-ID: <s5hr2mg81v5.wl-tiwai@suse.de> (raw)
In-Reply-To: <e959f23d6f6905ee606fadfda13e2bb37deed017.1525870886.git.mchehab+samsung@kernel.org>
On Wed, 09 May 2018 15:18:52 +0200,
Mauro Carvalho Chehab wrote:
>
> As we move stuff around, some doc references are broken. Fix some of
> them via this script:
> ./scripts/documentation-file-ref-check --fix-rst
>
> Manually checked if the produced result is valid, removing a few
> false-positives.
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
For sound stuff, feel free to take my ack (if it's not too late):
Acked-by: Takashi Iwai <tiwai@suse.de>
thanks,
Takashi
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-05-13 7:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1525870886.git.mchehab+samsung@kernel.org>
2018-05-09 13:18 ` [PATCH v2 03/11] docs: crypto_engine.rst: Fix two parse warnings Mauro Carvalho Chehab
2018-05-09 13:18 ` [PATCH v2 09/11] docs: Fix some broken references Mauro Carvalho Chehab
2018-05-09 17:15 ` Andrea Parri
2018-05-09 18:20 ` Mauro Carvalho Chehab
2018-05-09 19:11 ` Alan Stern
2018-05-09 19:41 ` Mauro Carvalho Chehab
2018-05-09 21:27 ` Andrea Parri
2018-05-09 19:20 ` Andrea Parri
2018-05-13 7:13 ` Takashi Iwai [this message]
2018-05-14 13:31 ` Masami Hiramatsu
2018-05-15 20:26 ` Stephen Boyd
2018-05-16 9:09 ` Charles Keepax
2018-05-16 15:12 ` Mathieu Poirier
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=s5hr2mg81v5.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=airlied@linux.ie \
--cc=alsa-devel@alsa-project.org \
--cc=boqun.feng@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=eparis@parisplace.org \
--cc=gregkh@linuxfoundation.org \
--cc=harryxiyou@gmail.com \
--cc=jcmvbkbc@gmail.com \
--cc=jmorris@namei.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=mark.rutland@arm.com \
--cc=mchehab+samsung@kernel.org \
--cc=npiggin@gmail.com \
--cc=perex@perex.cz \
--cc=royale@zerezo.com \
--cc=selinux@tycho.nsa.gov \
--cc=stern@rowland.harvard.edu \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.com \
--cc=xen-devel@lists.xenproject.org \
/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