All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: hpa@zytor.com
Cc: libc-alpha@sourceware.org, adhemerval.zanella@linaro.org,
	linux-api@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] Linux: Define struct termios2 in <termios.h> under _GNU_SOURCE [BZ #10339]
Date: Wed, 10 Apr 2019 08:50:24 +0200	[thread overview]
Message-ID: <87r2aaz74f.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <EF5CE34B-1A82-4391-B07E-DB832814AD1C@zytor.com> (hpa's message of "Tue, 09 Apr 2019 09:02:06 -0600")

* hpa:

> PowerPC doesn't need it at all.

Because the definition would be the same as struct termios?

I think we should still define struct termios2 using the struct termios
definition, and also define TCGETS2 and TCSETS2.  This way, applications
can use the struct termios2 type without affecting portability to POWER.

Thanks,
Florian

WARNING: multiple messages have this Message-ID (diff)
From: Florian Weimer <fweimer@redhat.com>
To: hpa@zytor.com
Cc: linux-api@vger.kernel.org, libc-alpha@sourceware.org,
	linuxppc-dev@lists.ozlabs.org, adhemerval.zanella@linaro.org
Subject: Re: [PATCH] Linux: Define struct termios2 in <termios.h> under _GNU_SOURCE [BZ #10339]
Date: Wed, 10 Apr 2019 08:50:24 +0200	[thread overview]
Message-ID: <87r2aaz74f.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <EF5CE34B-1A82-4391-B07E-DB832814AD1C@zytor.com> (hpa's message of "Tue, 09 Apr 2019 09:02:06 -0600")

* hpa:

> PowerPC doesn't need it at all.

Because the definition would be the same as struct termios?

I think we should still define struct termios2 using the struct termios
definition, and also define TCGETS2 and TCSETS2.  This way, applications
can use the struct termios2 type without affecting portability to POWER.

Thanks,
Florian

  reply	other threads:[~2019-04-10  6:50 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-09 10:47 [PATCH] Linux: Define struct termios2 in <termios.h> under _GNU_SOURCE [BZ #10339] Florian Weimer
2019-04-09 10:47 ` Florian Weimer
2019-04-09 15:02 ` hpa
2019-04-09 15:02   ` hpa
2019-04-10  6:50   ` Florian Weimer [this message]
2019-04-10  6:50     ` Florian Weimer
2019-04-15 15:54     ` hpa
2019-04-15 15:54       ` hpa
2019-04-09 15:07 ` hpa
2019-04-09 15:07   ` hpa
2019-04-09 16:04   ` Florian Weimer
2019-04-09 16:04     ` Florian Weimer
2019-04-10 20:24 ` Adhemerval Zanella
2019-04-10 20:24   ` Adhemerval Zanella
2019-04-11 11:07   ` Florian Weimer
2019-04-11 11:07     ` Florian Weimer
2019-04-11 12:53     ` Adhemerval Zanella
2019-04-11 12:53       ` Adhemerval Zanella
2019-04-12  7:50       ` Florian Weimer
2019-04-12  7:50         ` Florian Weimer
2019-04-15 12:28         ` Florian Weimer
2019-04-15 12:28           ` Florian Weimer
2019-04-15 15:53         ` hpa
2019-04-15 15:53           ` hpa
2019-04-15 17:22           ` Adhemerval Zanella
2019-04-15 17:22             ` Adhemerval Zanella
2019-04-17 22:04             ` H. Peter Anvin
2019-04-17 22:04               ` H. Peter Anvin
2019-04-18 11:09               ` Adhemerval Zanella
2019-04-18 11:09                 ` Adhemerval Zanella
2019-04-18 14:46                 ` hpa
2019-04-18 14:46                   ` hpa
2019-04-16  9:59           ` Florian Weimer
2019-04-16  9:59             ` Florian Weimer
2019-04-16 12:11             ` Adhemerval Zanella
2019-04-16 12:11               ` Adhemerval Zanella
2019-04-17 22:06             ` H. Peter Anvin
2019-04-17 22:06               ` H. Peter Anvin
2019-04-17 21:22 ` Joseph Myers
2019-04-17 21:22   ` Joseph Myers

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=87r2aaz74f.fsf@oldenburg2.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=hpa@zytor.com \
    --cc=libc-alpha@sourceware.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.