From: Nathan Sidwell <nathan@acm.org>
To: rbmj <rbmj@verizon.net>
Cc: gcc-patches@gcc.gnu.org, nathan@codesourcery.com, bkorb@gnu.org
Subject: Re: [PATCH] Fixincludes/VxWorks
Date: Sun, 10 Jun 2012 18:05:00 -0000 [thread overview]
Message-ID: <4FD4E020.80307@acm.org> (raw)
In-Reply-To: <4FCF863E.6090400@verizon.net>
On 06/06/12 17:33, rbmj wrote:
> Hi everyone,
>
> This patch series is the result of this [1] thread about fixincludes on VxWorks.
> It resolves bugs 53457 and 53378, and a few other issues that previously
> required manual intervention to fix for VxWorks header files.
From a vxworks POV these all look ok.
nathan
next prev parent reply other threads:[~2012-06-10 17:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-06 16:35 rbmj
2012-06-06 16:36 ` [PATCH 1/7] Add ability to skip the machine_name fixincludes fix rbmj
2012-06-06 16:37 ` [PATCH 2/7] Added assert fixinclude hack for VxWorks rbmj
2012-06-06 16:38 ` [PATCH 3/7] Add stdint.h wrapper " rbmj
2012-06-12 15:51 ` Joseph S. Myers
2012-06-12 20:21 ` rbmj
2012-06-12 20:33 ` Joseph S. Myers
2012-06-13 15:48 ` rbmj
2012-06-13 18:19 ` Joseph S. Myers
2012-06-20 20:00 ` rbmj
2012-06-21 7:35 ` Mike Stump
2012-06-25 19:54 ` rbmj
2012-06-25 20:16 ` Mike Stump
2012-06-25 20:40 ` rbmj
2012-06-25 23:37 ` Mike Stump
2012-06-06 16:38 ` [PATCH 4/7] Add unistd.h " rbmj
2012-06-06 16:39 ` [PATCH 5/7] Add fix to prevent accidental inclusion of regs.h on, VxWorks rbmj
2012-06-06 16:40 ` [PATCH 6/7] Add hack for ioctl() on VxWorks rbmj
2012-06-06 16:45 ` [PATCH 7/7] Add fix to make write() const correct " rbmj
2012-06-06 16:57 ` [PATCH] Fixincludes/VxWorks Bruce Korb
2012-06-06 17:16 ` Bruce Korb
2012-06-06 18:13 ` rbmj
2012-06-10 18:05 ` Nathan Sidwell [this message]
2012-06-10 21:30 ` Bruce Korb
2012-06-11 19:05 ` rbmj
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=4FD4E020.80307@acm.org \
--to=nathan@acm.org \
--cc=bkorb@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=nathan@codesourcery.com \
--cc=rbmj@verizon.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).