From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
linux-serial <linux-serial@vger.kernel.org>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Bagas Sanjaya <bagasdotme@gmail.com>,
linux-doc@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Subject: [PATCH v4 0/4] serial: RS485 kerneldoc/documentation improvements
Date: Thu, 29 Sep 2022 12:31:44 +0300 [thread overview]
Message-ID: <20220929093148.9468-1-ilpo.jarvinen@linux.intel.com> (raw)
RS485 documentation improvements. While doing the kerneldoc conversion,
a few other items came up so they're now included in this series.
v4:
- Remove wrong private: markers
- Fix grammar problems
v3:
- More fixes to kernel doc formatting (thanks to Jiri)
- Added a few other related improvements
v2:
- Include serial_rs485 into documentation
- Add * to multi-line flag descriptions
Ilpo Järvinen (4):
serial: Convert serial_rs485 to kernel doc
Documentation: rs485: Link reference properly
Documentation: rs485: Mention uart_get_rs485_mode()
Documentation: rs485: Fix struct referencing
.../driver-api/serial/serial-rs485.rst | 37 +++++++------
include/uapi/linux/serial.h | 55 ++++++++++++-------
2 files changed, 56 insertions(+), 36 deletions(-)
--
2.30.2
next reply other threads:[~2022-09-29 9:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 9:31 Ilpo Järvinen [this message]
2022-09-29 9:31 ` [PATCH v4 1/4] serial: Convert serial_rs485 to kernel doc Ilpo Järvinen
2022-09-30 9:27 ` Bagas Sanjaya
2022-09-29 9:31 ` [PATCH v4 2/4] Documentation: rs485: Link reference properly Ilpo Järvinen
2022-09-29 9:31 ` [PATCH v4 3/4] Documentation: rs485: Mention uart_get_rs485_mode() Ilpo Järvinen
2022-09-29 9:31 ` [PATCH v4 4/4] Documentation: rs485: Fix struct referencing Ilpo Järvinen
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=20220929093148.9468-1-ilpo.jarvinen@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@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
all inboxes | Powered by JetHome®