From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS3215 2.6.0.0/16 X-Spam-Status: No, score=-4.3 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,SPF_HELO_PASS,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (server2.sourceware.org [IPv6:2620:52:3:1:0:246e:9693:128c]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id D49811F8C6 for ; Mon, 2 Aug 2021 12:39:06 +0000 (UTC) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 1F1383853C0D for ; Mon, 2 Aug 2021 12:39:05 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1F1383853C0D DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1627907945; bh=+iwG4dwu630d56k0IddJZl8d8Tb26J8/7JwX5jp3IJ8=; h=To:Subject:Date:List-Id:List-Unsubscribe:List-Archive:List-Post: List-Help:List-Subscribe:From:Reply-To:Cc:From; b=K2ROhUZw0HyUO28CeIm77vrv0U4C8azkxZx8LjmWmAo5AQuQ53wImAeTdNdi3ulgE MV25HhclLz7/ZqImZrDW+WITKaPBYZgYqbopTafiDQWD1m3Sh8ngpS+rKV+GXib0eZ 932ikvLBP08C5nqh7TmsfMWwjCN8ec74axyHDDMg= Received: from mail-wm1-x32a.google.com (mail-wm1-x32a.google.com [IPv6:2a00:1450:4864:20::32a]) by sourceware.org (Postfix) with ESMTPS id 859343857402 for ; Mon, 2 Aug 2021 12:38:45 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 859343857402 Received: by mail-wm1-x32a.google.com with SMTP id m19so10335494wms.0 for ; Mon, 02 Aug 2021 05:38:45 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:cc:from:subject:message-id:date:user-agent :mime-version:content-language:content-transfer-encoding; bh=+iwG4dwu630d56k0IddJZl8d8Tb26J8/7JwX5jp3IJ8=; b=EPKQenLZm5okMWgUmkozHnsIGqAfMLL7WCBUcTI6F8Qi4UCqfvDy9VC8GjxUnAEACK lybIbT0J0cCfI/OJFqjOO+JON6eJmR8C0gyoMX1byIEFSy9ZJwTh2/VytDnXAUjyU79/ 9/POJBH1nJcZ+ItnobQ6y5I7yFoFgUSEMr9xe/Vv6VFbdxpWC0o8gGb39BUXgtcWD0H+ 68dhBZnt1a+RzzXz1H4eQmgOobauJ4PGHvpDP0N7o4wAAMf6H13ObjBNnv9KjGz+QTTP I/BOGN2XW+EtQeXX8SDosktL5FFBwlqYYB8zym4Lw30/BgptcH06BPuxDcdLVLSS214q gmBw== X-Gm-Message-State: AOAM532kxbkhkkFGTnp1X5+r86Pq5DaPRsn5x29WCnatX13FaNrE5KpG Rv5//mELfQUG7im4tvq7mZyJRJRdWMY= X-Google-Smtp-Source: ABdhPJziT2hGn88fhyV5m6uDGOZe4vRiWnpKzETiW6DtTKbGsi5lbt+/ti5aGWb1djGpfbimwkssQw== X-Received: by 2002:a05:600c:304a:: with SMTP id n10mr16999122wmh.79.1627907924730; Mon, 02 Aug 2021 05:38:44 -0700 (PDT) Received: from [10.8.0.10] ([195.53.121.100]) by smtp.gmail.com with ESMTPSA id s2sm9992886wmh.46.2021.08.02.05.38.43 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 02 Aug 2021 05:38:44 -0700 (PDT) To: Glibc , "linux-kernel@vger.kernel.org" Subject: Document the types "struct termios" and "struct termios2" Message-ID: Date: Mon, 2 Aug 2021 14:38:43 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: libc-alpha@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-alpha mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: "Alejandro Colomar \(man-pages\) via Libc-alpha" Reply-To: "Alejandro Colomar \(man-pages\)" Cc: =?UTF-8?Q?Pali_Roh=c3=a1r?= Errors-To: libc-alpha-bounces+e=80x24.org@sourceware.org Sender: "Libc-alpha" Hi, From a few patches of Pali and their subsequent discussions, 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/