From: Joel Brobecker <brobecker@adacore.com>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/3] Fix -Werror=pointer-sign warnings
Date: Fri, 07 Feb 2014 11:42:00 -0000 [thread overview]
Message-ID: <20140207114208.GG5485@adacore.com> (raw)
In-Reply-To: <1391759958-972-3-git-send-email-yao@codesourcery.com>
> 2014-02-07 Yao Qi <yao@codesourcery.com>
>
> * gnu-nat.c (gnu_read_inferior): Change 'copy_count' type to
> mach_msg_type_number_t.
> (gnu_write_inferior): Likewise.
You did not say obvious on this one, but it looks that way to me.
Anyways, looks good.
--
Joel
next prev parent reply other threads:[~2014-02-07 11:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-07 8:01 [PATCH 0/3] Unbreak build on hurd Yao Qi
2014-02-07 8:01 ` [PATCH 1/3 OBV] Fix -Wformat warnings in gnu-nat.c Yao Qi
2014-02-16 7:38 ` Thomas Schwinge
2014-02-17 3:32 ` Yao Qi
2014-02-07 8:01 ` [PATCH 2/3] Fix -Werror=pointer-sign warnings Yao Qi
2014-02-07 11:42 ` Joel Brobecker [this message]
2014-02-16 7:39 ` Thomas Schwinge
2014-02-17 3:32 ` Yao Qi
2014-02-07 8:01 ` [PATCH 3/3] Find and link with -lmachuser -lhurduser Yao Qi
2014-02-16 7:49 ` Thomas Schwinge
2014-02-17 2:17 ` Yao Qi
2014-02-25 5:10 ` Samuel Thibault
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=20140207114208.GG5485@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=yao@codesourcery.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