Linux Documentation
 help / color / mirror / Atom feed
From: Carlos Bilbao <carlos.bilbao@amd.com>
To: <corbet@lwn.net>, <lukas.bulwahn@gmail.com>, <ojeda@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-doc@vger.kernel.org>,
	<bilbao@vt.edu>, <jm@goyeneche.es>,
	Carlos Bilbao <carlos.bilbao@amd.com>
Subject: [PATCH v2 1/2] docs: Update maintainer of kernel-docs.rst
Date: Mon, 21 Nov 2022 12:16:25 -0600	[thread overview]
Message-ID: <20221121181626.149558-2-carlos.bilbao@amd.com> (raw)
In-Reply-To: <20221121181626.149558-1-carlos.bilbao@amd.com>

Set new maintainer of the Index of Further Kernel Documentation (document
process/kernel_docs.rst). See Link for further context. Also remove line
that keeps record of last update of the text -this information is already
available elsewhere.

Link: https://lore.kernel.org/lkml/20221118170942.2588412-1-carlos.bilbao@amd.com/
Signed-off-by: Carlos Bilbao <carlos.bilbao@amd.com>
---
 Documentation/process/kernel-docs.rst | 8 +++-----
 MAINTAINERS                           | 5 +++++
 2 files changed, 8 insertions(+), 5 deletions(-)

diff --git a/Documentation/process/kernel-docs.rst b/Documentation/process/kernel-docs.rst
index 306ad373a002..8574b577d50a 100644
--- a/Documentation/process/kernel-docs.rst
+++ b/Documentation/process/kernel-docs.rst
@@ -3,9 +3,6 @@
 Index of Further Kernel Documentation
 =====================================
 
-Initial Author: Juan-Mariano de Goyeneche (<jmseyas@dit.upm.es>;
-email address is defunct now.)
-
 The need for a document like this one became apparent in the
 linux-kernel mailing list as the same questions, asking for pointers
 to information, appeared again and again.
@@ -614,7 +611,8 @@ Miscellaneous
 
 -------
 
-Document last updated on Tue 2016-Sep-20
+This document was originally based on:
 
-This document is based on:
  https://www.dit.upm.es/~jmseyas/linux/kernel/hackers-docs.html
+
+and written by Juan-Mariano de Goyenche
diff --git a/MAINTAINERS b/MAINTAINERS
index 6f2ec7c71a4c..91b668dc1217 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -10017,6 +10017,11 @@ F:	Documentation/hwmon/ina2xx.rst
 F:	drivers/hwmon/ina2xx.c
 F:	include/linux/platform_data/ina2xx.h
 
+INDEX OF FURTHER KERNEL DOCUMENTATION
+M:      Carlos Bilbao <carlos.bilbao@amd.com>
+S:      Maintained
+F:      Documentation/process/kernel-docs.rst
+
 INDUSTRY PACK SUBSYSTEM (IPACK)
 M:	Samuel Iglesias Gonsalvez <siglesias@igalia.com>
 M:	Jens Taprogge <jens.taprogge@taprogge.org>
-- 
2.34.1


  reply	other threads:[~2022-11-21 18:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-21 18:16 [PATCH v2 0/2] kernel-docs: New maintainer and Spanish translation Carlos Bilbao
2022-11-21 18:16 ` Carlos Bilbao [this message]
2022-11-21 20:16   ` [PATCH v2 1/2] docs: Update maintainer of kernel-docs.rst Miguel Ojeda
2022-11-21 18:16 ` [PATCH v2 2/2] docs/sp_SP: Add process kernel-docs translation Carlos Bilbao
2022-11-21 20:19   ` Miguel Ojeda

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=20221121181626.149558-2-carlos.bilbao@amd.com \
    --to=carlos.bilbao@amd.com \
    --cc=bilbao@vt.edu \
    --cc=corbet@lwn.net \
    --cc=jm@goyeneche.es \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=ojeda@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox