From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Karsten Keil <isdn@linux-pingi.de>,
netdev@vger.kernel.org
Subject: [PATCH 06/10] isdn: mISDN: remove a bogus reference to a non-existing doc
Date: Mon, 20 May 2019 11:47:35 -0300 [thread overview]
Message-ID: <fc32252984b91ad726d6ee2845a71e204e9afe25.1558362030.git.mchehab+samsung@kernel.org> (raw)
In-Reply-To: <cover.1558362030.git.mchehab+samsung@kernel.org>
The mISDN driver was added on those commits:
960366cf8dbb ("Add mISDN DSP")
1b2b03f8e514 ("Add mISDN core files")
04578dd330f1 ("Define AF_ISDN and PF_ISDN")
e4ac9bc1f668 ("Add mISDN driver")
None of them added a Documentation/isdn/mISDN.cert file.
Also, whatever were supposed to be written there on that time,
probably doesn't make any sense nowadays, as I doubt isdn would
have any massive changes.
So, let's just get rid of the broken reference, in order to
shut up a warning produced by ./scripts/documentation-file-ref-check.
Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
---
drivers/isdn/mISDN/dsp_core.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/isdn/mISDN/dsp_core.c b/drivers/isdn/mISDN/dsp_core.c
index cd036e87335a..038e72a84b33 100644
--- a/drivers/isdn/mISDN/dsp_core.c
+++ b/drivers/isdn/mISDN/dsp_core.c
@@ -4,8 +4,6 @@
* Karsten Keil (keil@isdn4linux.de)
*
* This file is (c) under GNU PUBLIC LICENSE
- * For changes and modifications please read
- * ../../../Documentation/isdn/mISDN.cert
*
* Thanks to Karsten Keil (great drivers)
* Cologne Chip (great chips)
--
2.21.0
next prev parent reply other threads:[~2019-05-20 14:48 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 14:47 [PATCH 00/10] Fix broken documentation references at v5.2-rc1 Mauro Carvalho Chehab
2019-05-20 14:47 ` [PATCH 01/10] scripts/documentation-file-ref-check: better handle translations Mauro Carvalho Chehab
2019-05-20 14:47 ` [PATCH 02/10] scripts/documentation-file-ref-check: exclude false-positives Mauro Carvalho Chehab
2019-05-20 14:47 ` [PATCH 03/10] scripts/documentation-file-ref-check: improve tools ref handling Mauro Carvalho Chehab
2019-05-20 14:47 ` [PATCH 04/10] scripts/documentation-file-ref-check: teach about .txt -> .yaml renames Mauro Carvalho Chehab
2019-05-20 14:47 ` [PATCH 05/10] ABI: sysfs-devices-system-cpu: point to the right docs Mauro Carvalho Chehab
2019-05-20 14:47 ` Mauro Carvalho Chehab [this message]
2019-05-20 14:47 ` [PATCH 07/10] mfd: madera: point to the right pinctrl binding file Mauro Carvalho Chehab
2019-05-20 15:42 ` Charles Keepax
2019-05-20 15:42 ` Charles Keepax
2019-05-20 18:48 ` Mauro Carvalho Chehab
2019-05-20 18:48 ` Mauro Carvalho Chehab
2019-05-20 14:47 ` [PATCH 08/10] dt: fix refs that were renamed to json with the same file name Mauro Carvalho Chehab
2019-05-20 14:47 ` Mauro Carvalho Chehab
2019-05-20 15:57 ` Rob Herring
2019-05-20 15:57 ` Rob Herring
2019-05-20 16:13 ` Mauro Carvalho Chehab
2019-05-20 16:13 ` Mauro Carvalho Chehab
2019-05-20 23:00 ` Rob Herring
2019-05-20 23:00 ` Rob Herring
2019-05-20 14:47 ` [PATCH 09/10] dt: fix broken references to nand.txt Mauro Carvalho Chehab
2019-05-20 14:47 ` Mauro Carvalho Chehab
2019-05-20 14:47 ` Mauro Carvalho Chehab
2019-05-20 14:47 ` Mauro Carvalho Chehab
2019-05-20 15:37 ` Miquel Raynal
2019-05-20 15:37 ` Miquel Raynal
2019-05-20 15:37 ` Miquel Raynal
2019-05-20 15:37 ` Miquel Raynal
2019-05-20 14:47 ` [PATCH 10/10] docs: fix broken documentation links Mauro Carvalho Chehab
2019-05-20 14:47 ` Mauro Carvalho Chehab
2019-05-20 14:47 ` Mauro Carvalho Chehab
2019-05-20 14:47 ` [Xen-devel] " Mauro Carvalho Chehab
2019-05-20 14:47 ` Mauro Carvalho Chehab
2019-05-20 14:47 ` Mauro Carvalho Chehab
2019-05-20 14:47 ` Mauro Carvalho Chehab
2019-05-20 14:47 ` mchehab+samsung
2019-05-20 14:47 ` Mauro Carvalho Chehab
2019-05-20 15:05 ` Wolfram Sang
2019-05-20 15:05 ` Wolfram Sang
2019-05-20 15:05 ` [Xen-devel] " Wolfram Sang
2019-05-20 15:05 ` Wolfram Sang
2019-05-20 15:05 ` Wolfram Sang
2019-05-20 15:05 ` Wolfram Sang
2019-05-20 15:05 ` wsa
2019-05-20 15:05 ` Wolfram Sang
2019-05-20 15:05 ` Wolfram Sang
2019-05-21 22:56 ` Federico Vaga
2019-05-21 22:56 ` Federico Vaga
2019-05-21 22:56 ` [Xen-devel] " Federico Vaga
2019-05-21 22:56 ` Federico Vaga
2019-05-21 22:56 ` Federico Vaga
2019-05-21 22:56 ` Federico Vaga
2019-05-21 22:56 ` federico.vaga
2019-05-21 22:56 ` Federico Vaga
2019-05-21 22:56 ` Federico Vaga
2019-05-27 8:43 ` Rafael J. Wysocki
2019-05-27 8:43 ` [Devel] " Rafael J. Wysocki
2019-05-27 8:43 ` Rafael J. Wysocki
2019-05-27 8:43 ` [Xen-devel] " Rafael J. Wysocki
2019-05-27 8:43 ` Rafael J. Wysocki
2019-05-27 8:43 ` Rafael J. Wysocki
2019-05-27 8:43 ` Rafael J. Wysocki
2019-05-27 8:43 ` Rafael J. Wysocki
2019-05-27 8:43 ` rafael
2019-05-27 8:43 ` Rafael J. Wysocki
2019-05-27 8:43 ` Rafael J. Wysocki
2019-05-27 8:43 ` Rafael J. Wysocki
2019-05-21 22:54 ` [PATCH 00/10] Fix broken documentation references at v5.2-rc1 Federico Vaga
2019-05-22 0:26 ` Mauro Carvalho Chehab
2019-05-22 20:18 ` Federico Vaga
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=fc32252984b91ad726d6ee2845a71e204e9afe25.1558362030.git.mchehab+samsung@kernel.org \
--to=mchehab+samsung@kernel.org \
--cc=corbet@lwn.net \
--cc=isdn@linux-pingi.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=netdev@vger.kernel.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 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.