public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Linux Media Mailing List <linux-media@vger.kernel.org>,
	Sean Young <sean@mess.org>
Cc: linuxarm@huawei.com, mauro.chehab@huawei.com,
	Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] Improve LIRC documentation
Date: Thu, 26 Nov 2020 14:00:54 +0100	[thread overview]
Message-ID: <cover.1606395586.git.mchehab+huawei@kernel.org> (raw)

Hi Sean,

Those two patches improve LIRC uAPI docs by adding the structs documented at
lirc.h to the output of Documentation/output/userspace-api/media/rc/lirc-dev-intro.html

Please review.

Mauro Carvalho Chehab (2):
  media: docs: uAPI: rc: dual-license the docs with GPL v2
  media: rc: improve LIRC documentation

 Documentation/userspace-api/media/rc/keytable.c.rst |  2 +-
 .../userspace-api/media/rc/lirc-dev-intro.rst       | 13 ++++++++++---
 Documentation/userspace-api/media/rc/lirc-dev.rst   |  2 +-
 Documentation/userspace-api/media/rc/lirc-func.rst  |  2 +-
 .../userspace-api/media/rc/lirc-get-features.rst    |  2 +-
 .../userspace-api/media/rc/lirc-get-rec-mode.rst    |  2 +-
 .../media/rc/lirc-get-rec-resolution.rst            |  2 +-
 .../userspace-api/media/rc/lirc-get-send-mode.rst   |  2 +-
 .../userspace-api/media/rc/lirc-get-timeout.rst     |  2 +-
 .../userspace-api/media/rc/lirc-header.rst          |  2 +-
 Documentation/userspace-api/media/rc/lirc-read.rst  |  2 +-
 .../media/rc/lirc-set-measure-carrier-mode.rst      |  2 +-
 .../media/rc/lirc-set-rec-carrier-range.rst         |  2 +-
 .../userspace-api/media/rc/lirc-set-rec-carrier.rst |  2 +-
 .../media/rc/lirc-set-rec-timeout-reports.rst       |  2 +-
 .../userspace-api/media/rc/lirc-set-rec-timeout.rst |  2 +-
 .../media/rc/lirc-set-send-carrier.rst              |  2 +-
 .../media/rc/lirc-set-send-duty-cycle.rst           |  2 +-
 .../media/rc/lirc-set-transmitter-mask.rst          |  2 +-
 .../media/rc/lirc-set-wideband-receiver.rst         |  2 +-
 Documentation/userspace-api/media/rc/lirc-write.rst |  2 +-
 Documentation/userspace-api/media/rc/rc-intro.rst   |  2 +-
 Documentation/userspace-api/media/rc/rc-protos.rst  |  2 +-
 .../userspace-api/media/rc/rc-sysfs-nodes.rst       |  2 +-
 .../userspace-api/media/rc/rc-table-change.rst      |  2 +-
 Documentation/userspace-api/media/rc/rc-tables.rst  |  2 +-
 .../userspace-api/media/rc/remote_controllers.rst   |  2 +-
 include/uapi/linux/lirc.h                           |  2 +-
 28 files changed, 37 insertions(+), 30 deletions(-)

-- 
2.28.0



             reply	other threads:[~2020-11-26 13:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-26 13:00 Mauro Carvalho Chehab [this message]
2020-11-26 13:00 ` [PATCH 1/2] media: docs: uAPI: rc: dual-license the docs with GPL v2 Mauro Carvalho Chehab
2020-11-26 13:00 ` [PATCH 2/2] media: rc: improve LIRC documentation Mauro Carvalho Chehab
2020-11-26 13:13 ` [PATCH 0/2] Improve " Sean Young

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=cover.1606395586.git.mchehab+huawei@kernel.org \
    --to=mchehab+huawei@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=mauro.chehab@huawei.com \
    --cc=mchehab@kernel.org \
    --cc=sean@mess.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