From: Wolfram Sang <wsa@the-dreams.de>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Cc: Andrew Lunn <andrew@lunn.ch>, Andy Lutomirski <luto@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Linus Walleij <linus.walleij@linaro.org>,
Will Deacon <will.deacon@arm.com>,
Pavel Tatashin <pasha.tatashin@oracle.com>,
Paul Mackerras <paulus@samba.org>,
Alessia Mantegazza <amantegazza@vaga.pv.it>,
Jakub Wilk <jwilk@jwilk.net>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
"Paul E. McKenney" <paulmck@linux.ibm.com>,
Kevin Hilman <khilman@baylibre.com>,
James Morris <jmorris@namei.org>,
linux-acpi@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
xen-devel@lists.xenproject.org,
Alexander Popov <alex.popov@linux.com>, Qian Cai <cai@lca.pw>,
Al Viro <viro@zeniv.linux.org.uk>,
Thomas Preston <thomas.preston@codethink.co.uk>,
Thomas Gleixner <tglx@linutronix.de>,
Kairui Song <kasong@redhat.com>, Ding Xiang <di>
Subject: Re: [PATCH 22/22] docs: fix broken documentation links
Date: Thu, 30 May 2019 09:21:14 +0200 [thread overview]
Message-ID: <20190530072110.GA1776@kunai> (raw)
In-Reply-To: <f9fecacbe4ce0b2b3aed38d71ae3753f2daf3ce3.1559171394.git.mchehab+samsung@kernel.org>
[-- Attachment #1.1: Type: text/plain, Size: 366 bytes --]
On Wed, May 29, 2019 at 08:23:53PM -0300, Mauro Carvalho Chehab wrote:
> Mostly due to x86 and acpi conversion, several documentation
> links are still pointing to the old file. Fix them.
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Didn't I ack this already?
For the I2C part:
Reviewed-by: Wolfram Sang <wsa@the-dreams.de>
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 183 bytes --]
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2019-05-30 7:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 23:23 [PATCH 00/22] Some documentation fixes Mauro Carvalho Chehab
2019-05-29 23:23 ` [PATCH 03/22] dt: fix broken references to nand.txt Mauro Carvalho Chehab
2019-05-29 23:23 ` [PATCH 22/22] docs: fix broken documentation links Mauro Carvalho Chehab
2019-05-30 7:21 ` Wolfram Sang [this message]
2019-05-30 20:17 ` Federico Vaga
2019-05-30 22:49 ` Michael S. Tsirkin
2019-06-03 7:34 ` Christophe Leroy
2019-06-04 9:46 ` Mauro Carvalho Chehab
2019-06-04 9:58 ` Mauro Carvalho Chehab
2019-06-03 15:41 ` Mark Brown
2019-06-04 6:12 ` Bhupesh Sharma
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=20190530072110.GA1776@kunai \
--to=wsa@the-dreams.de \
--cc=alex.popov@linux.com \
--cc=amantegazza@vaga.pv.it \
--cc=andrew@lunn.ch \
--cc=benh@kernel.crashing.org \
--cc=bgolaszewski@baylibre.com \
--cc=cai@lca.pw \
--cc=catalin.marinas@arm.com \
--cc=jmorris@namei.org \
--cc=jwilk@jwilk.net \
--cc=kasong@redhat.com \
--cc=khilman@baylibre.com \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=mingo@redhat.com \
--cc=pasha.tatashin@oracle.com \
--cc=paulmck@linux.ibm.com \
--cc=paulus@samba.org \
--cc=tglx@linutronix.de \
--cc=thomas.preston@codethink.co.uk \
--cc=viro@zeniv.linux.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).