From: "Joseph S. Myers" <joseph@codesourcery.com>
To: libc-ports@sourceware.org, Richard Henderson <rth@twiddle.net>,
Chris Metcalf <cmetcalf@tilera.com>
Subject: Re: PATCH: Add __syscall_slong_t and __syscall_ulong_t
Date: Wed, 16 May 2012 10:31:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1205161028570.11537@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAMe9rOqh-VbhrzyPbOfvoJ_xarMSf57zbniEr0sRK1+StVpy7g@mail.gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 598 bytes --]
On Tue, 15 May 2012, H.J. Lu wrote:
> On Tue, May 15, 2012 at 9:41 AM, Roland McGrath <roland@hack.frob.com> wrote:
> > OK, so it's used in public struct types. The change is fine then.
> > I don't care either way about __snseconds_t.
> >
> > Thanks,
> > Roland
>
> I checked it in. I am checking in this patch to remove __snseconds_t.
Richard, Chris, you'll want to update the alpha and linux-generic
typesizes.h files in line with these changes to add __SYSCALL_SLONG_TYPE
and __SYSCALL_ULONG_TYPE and remove __SNSECONDS_T_TYPE.
--
Joseph S. Myers
joseph@codesourcery.com
next parent reply other threads:[~2012-05-16 10:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120412012017.GA27647@intel.com>
[not found] ` <20120514220816.DDDB42C08E@topped-with-meat.com>
[not found] ` <CAMe9rOpEUO2aKJ4494knAhwuuM7d3Ztz8jNUph1psWrJZozjMQ@mail.gmail.com>
[not found] ` <20120515164158.17BBD2C086@topped-with-meat.com>
[not found] ` <CAMe9rOqh-VbhrzyPbOfvoJ_xarMSf57zbniEr0sRK1+StVpy7g@mail.gmail.com>
2012-05-16 10:31 ` Joseph S. Myers [this message]
2012-05-16 13:45 ` [PATCH] linux-generic: fix typesizes.h to match recent core changes Chris Metcalf
2012-05-16 14:12 ` Joseph S. Myers
2012-05-18 13:39 ` Joseph S. Myers
2012-05-18 17:19 ` [PATCH] linux-generic: add __FSWORD_T_TYPE to <bits/typesizes.h> Chris Metcalf
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=Pine.LNX.4.64.1205161028570.11537@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=cmetcalf@tilera.com \
--cc=libc-ports@sourceware.org \
--cc=rth@twiddle.net \
/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).