From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Steve Ellcey <sellcey@mips.com>
Cc: libc-ports@sourceware.org
Subject: Re: Building syscall.h on mips
Date: Wed, 23 May 2012 00:06:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1205230005390.8022@digraph.polyomino.org.uk> (raw)
In-Reply-To: <1337726427.21213.155.camel@ubuntu-sellcey>
On Tue, 22 May 2012, Steve Ellcey wrote:
> Ok, I think I have it now. With these -D flags, I get similar but not
> identical sets for the three ifdef's. I would have liked to use
> _MIPS_SIM_ABI32, etc in the -D instead of 1,2,3 but that did not seem to
> work.
>
> How does this patch look?
It looks good but appears to have a line wrapped so it doesn't apply
cleanly - could you send a patch with whitespace preserved, and a
ChangeLog entry to go in ChangeLog.mips?
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2012-05-23 0:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 21:02 Steve Ellcey
2012-05-22 21:10 ` Joseph S. Myers
2012-05-22 22:40 ` Steve Ellcey
2012-05-23 0:06 ` Joseph S. Myers [this message]
2012-05-23 15:47 ` Steve Ellcey
2012-05-23 18:49 ` Joseph S. 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=Pine.LNX.4.64.1205230005390.8022@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=libc-ports@sourceware.org \
--cc=sellcey@mips.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).