From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Jiri Slaby <jirislaby@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-serial <linux-serial@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Andy Shevchenko <andy.shevchenko@gmail.com>
Subject: Re: [PATCH v2] serial: Convert serial_rs485 to kernel doc
Date: Tue, 27 Sep 2022 14:07:39 +0300 (EEST) [thread overview]
Message-ID: <958bf61e-6d85-4843-128-2f76e632b920@linux.intel.com> (raw)
In-Reply-To: <d571f4ec-494e-d9fd-70c4-ab96a21abf03@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1529 bytes --]
On Tue, 27 Sep 2022, Jiri Slaby wrote:
> On 27. 09. 22, 12:47, Ilpo Järvinen wrote:
> > For reasons unknown to me, the formatting in the flags doesn't produce the
> > effect promised by kerneldoc's documentation:
> >
> > https://www.kernel.org/doc/html/latest/doc-guide/kernel-doc.html#return-values
>
> Returns are special.
Might be but I understood that formatting thing to be more general.
> > * Serial interface for controlling RS485 settings on chips with suitable
> > * support. Set with TIOCSRS485 and get with TIOCGRS485 if supported by
> > your
> > * platform. The set function returns the new state, with any unsupported
> > bits
> > * reverted appropriately.
> > + *
> > + * serial_rs485::flags bits are:
>
> Put one more \n here.
>
> > + * * %SER_RS485_ENABLED - RS485 enabled.
> > + * * %SER_RS485_RTS_ON_SEND - Logical level for RTS pin when sending.
> > + * * %SER_RS485_RTS_AFTER_SEND - Logical level for RTS pin after
> > sent.
> > + * * %SER_RS485_RX_DURING_TX - Full-duplex RS485 line.
> > + * * %SER_RS485_TERMINATE_BUS - Enable bus termination (if
> > supported).
> > + * * %SER_RS485_ADDRB - Enable RS485 addressing mode.
> > + * * %SER_RS485_ADDR_RECV - Receive address filter (enables @addr_recv).
> > + * * Requires %SER_RS485_ADDRB.
>
> And perhaps remove the second * here?
It gave me error earlier but now when I added also that newline above you
suggested, it seems to no longer triggers the error. Thus, I ended up
making both of the changes you suggested.
--
i.
next prev parent reply other threads:[~2022-09-27 11:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 10:47 [PATCH v2] serial: Convert serial_rs485 to kernel doc Ilpo Järvinen
2022-09-27 10:56 ` Jiri Slaby
2022-09-27 11:07 ` Ilpo Järvinen [this message]
2022-09-27 10:58 ` Jiri Slaby
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=958bf61e-6d85-4843-128-2f76e632b920@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@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;
as well as URLs for NNTP newsgroup(s).