From: "Pali Rohár" <pali@kernel.org>
To: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
Cc: Glibc <libc-alpha@sourceware.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-serial@vger.kernel.org
Subject: Re: Document the types "struct termios" and "struct termios2"
Date: Mon, 2 Aug 2021 14:50:34 +0200 [thread overview]
Message-ID: <20210802125034.gubtf24tsm7lkh3k@pali> (raw)
In-Reply-To: <ef6a352d-4926-9cdc-9894-e387866a00c4@gmail.com>
+ linux-serial
On Monday 02 August 2021 14:38:43 Alejandro Colomar (man-pages) wrote:
> Hi,
>
> From a few patches of Pali and their subsequent discussions,
For others, link to patch with code example:
https://lore.kernel.org/linux-man/20210801135146.14849-1-pali@kernel.org/
And links to other discussions:
https://lore.kernel.org/linux-man/20210725225506.7404-1-pali@kernel.org/t/#u
https://lore.kernel.org/linux-man/20210730105353.10424-1-pali@kernel.org/t/#u
https://lore.kernel.org/linux-man/20210730153044.23673-1-pali@kernel.org/t/#u
> it was clear
> that those types need to be documented (the most appropriate place being
> system_data_types(7), with link pages termios-struct(3) and
> termios2-struct(3)).
>
> The most important part (the one we had problems with) being which headers
> should be included for each type (and for each version of the type
> (kernel/glibc)). That includes the recommended header, and other headers
> that _shall_ also provide the type.
>
> Is there someone that knows those types enough to write such documentation
> and wants to do it? :)
>
> Thanks,
>
> Alex
>
> --
> Alejandro Colomar
> Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
> http://www.alejandro-colomar.es/
next prev parent reply other threads:[~2021-08-02 12:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 12:38 Document the types "struct termios" and "struct termios2" Alejandro Colomar (man-pages)
2021-08-02 12:50 ` Pali Rohár [this message]
2021-08-02 13:07 ` Alejandro Colomar (man-pages)
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=20210802125034.gubtf24tsm7lkh3k@pali \
--to=pali@kernel.org \
--cc=alx.manpages@gmail.com \
--cc=libc-alpha@sourceware.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).