From: Joseph Myers <joseph@codesourcery.com>
To: Zack Weinberg <zackw@panix.com>
Cc: <libc-alpha@sourceware.org>, <Marcus.Shawcroft@arm.com>,
<rth@redhat.com>, <carlos@redhat.com>, <vapier@gentoo.org>,
<david@holsgrove.tech>, <cmetcalf@mellanox.com>,
<szabolcs.nagy@arm.com>
Subject: Re: Fix mcontext_t sigcontext namespace (bug 21457)
Date: Mon, 26 Jun 2017 22:26:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1706262222060.9666@digraph.polyomino.org.uk> (raw)
In-Reply-To: <bf28209a-42d0-921e-d8c6-e2747a92f03f@panix.com>
On Mon, 26 Jun 2017, Zack Weinberg wrote:
> Independent of that, this is finicky enough and has enough
> kernel-interface implications that I think it had better have
> architecture maintainer reviews for, at least, all architectures where
> you copied the contents of struct sigcontext into the definition of
> mcontext_t.
Ping of <https://sourceware.org/ml/libc-alpha/2017-06/msg00946.html> for
architecture maintainers for aarch64, alpha, hppa, ia64, microblaze, tile.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2017-06-26 22:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 17:53 Joseph Myers
2017-06-26 11:12 ` Ping " Joseph Myers
2017-06-26 21:06 ` Zack Weinberg
2017-06-26 22:26 ` Joseph Myers [this message]
2017-06-29 19:51 ` Joseph Myers
2017-06-30 15:59 ` Szabolcs Nagy
2017-07-21 20:36 ` Chris Metcalf
2017-06-27 11:41 ` Joseph Myers
2017-06-27 13:11 ` Carlos O'Donell
2017-06-27 13:32 ` Joseph Myers
2017-06-27 14:43 ` Szabolcs Nagy
2017-06-27 15:11 ` Joseph Myers
2017-06-27 15:28 ` Szabolcs Nagy
2017-06-27 15:53 ` Florian Weimer
2017-06-27 15:56 ` Joseph Myers
2017-06-27 18:41 ` Florian Weimer
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=alpine.DEB.2.20.1706262222060.9666@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=Marcus.Shawcroft@arm.com \
--cc=carlos@redhat.com \
--cc=cmetcalf@mellanox.com \
--cc=david@holsgrove.tech \
--cc=libc-alpha@sourceware.org \
--cc=rth@redhat.com \
--cc=szabolcs.nagy@arm.com \
--cc=vapier@gentoo.org \
--cc=zackw@panix.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).