Linux Documentation
 help / color / mirror / Atom feed
From: Tomas Winkler <tomas.winkler@intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Alexander Usyskin <alexander.usyskin@intel.com>,
	linux-kernel@vger.kernel.org,
	Tomas Winkler <tomas.winkler@intel.com>,
	Jonathan Corbet <corbet@lwn.net>,
	linux-doc@vger.kernel.org
Subject: [char-misc-next 0/7] mei: docs: move documentation under driver-api
Date: Mon,  3 Jun 2019 12:13:59 +0300	[thread overview]
Message-ID: <20190603091406.28915-1-tomas.winkler@intel.com> (raw)

Move mei documentation under driver-api, convert the docs to rst,
fix the outdated information, update broken links, and add new docs.


Tomas Winkler (7):
  mei: docs: move documentation under driver-api
  mei: docs: move iamt docs to a iamt.rst file
  mei: docs: update mei documentation
  mei: docs: update mei client bus documentation.
  mei: docs: add a short description for nfc behind mei
  mei: docs: add hdcp documentation
  mei: docs: fix broken links in iamt documentation.

 Documentation/driver-api/index.rst            |   1 +
 Documentation/driver-api/mei/hdcp.rst         |  32 +++
 Documentation/driver-api/mei/iamt.rst         | 101 +++++++
 Documentation/driver-api/mei/index.rst        |  23 ++
 .../driver-api/mei/mei-client-bus.rst         | 168 +++++++++++
 Documentation/driver-api/mei/mei.rst          | 176 ++++++++++++
 Documentation/driver-api/mei/nfc.rst          |  28 ++
 .../misc-devices/mei/mei-client-bus.txt       | 141 ----------
 Documentation/misc-devices/mei/mei.txt        | 266 ------------------
 MAINTAINERS                                   |   2 +-
 drivers/misc/mei/hdcp/mei_hdcp.c              |  11 +-
 11 files changed, 534 insertions(+), 415 deletions(-)
 create mode 100644 Documentation/driver-api/mei/hdcp.rst
 create mode 100644 Documentation/driver-api/mei/iamt.rst
 create mode 100644 Documentation/driver-api/mei/index.rst
 create mode 100644 Documentation/driver-api/mei/mei-client-bus.rst
 create mode 100644 Documentation/driver-api/mei/mei.rst
 create mode 100644 Documentation/driver-api/mei/nfc.rst
 delete mode 100644 Documentation/misc-devices/mei/mei-client-bus.txt
 delete mode 100644 Documentation/misc-devices/mei/mei.txt

-- 
2.20.1


             reply	other threads:[~2019-06-03  9:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-03  9:13 Tomas Winkler [this message]
2019-06-03  9:14 ` [char-misc-next 1/7] mei: docs: move documentation under driver-api Tomas Winkler
2019-06-03  9:14 ` [char-misc-next 2/7] mei: docs: move iamt docs to a iamt.rst file Tomas Winkler
2019-06-03  9:14 ` [char-misc-next 3/7] mei: docs: update mei documentation Tomas Winkler
2019-06-06 13:16   ` Greg Kroah-Hartman
2019-06-06 13:38     ` Winkler, Tomas
2019-06-03  9:14 ` [char-misc-next 4/7] mei: docs: update mei client bus documentation Tomas Winkler
2019-06-03  9:14 ` [char-misc-next 5/7] mei: docs: add a short description for nfc behind mei Tomas Winkler
2019-06-03  9:14 ` [char-misc-next 6/7] mei: docs: add hdcp documentation Tomas Winkler
2019-06-03  9:14 ` [char-misc-next 7/7] mei: docs: fix broken links in iamt documentation Tomas Winkler

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=20190603091406.28915-1-tomas.winkler@intel.com \
    --to=tomas.winkler@intel.com \
    --cc=alexander.usyskin@intel.com \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox