From: Thomas Schwinge <thomas@codesourcery.com>
To: Yao Qi <yao@codesourcery.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/3 OBV] Fix -Wformat warnings in gnu-nat.c
Date: Sun, 16 Feb 2014 07:38:00 -0000 [thread overview]
Message-ID: <87iosfv763.fsf@kepler.schwinge.homeip.net> (raw)
In-Reply-To: <1391759958-972-2-git-send-email-yao@codesourcery.com>
[-- Attachment #1: Type: text/plain, Size: 758 bytes --]
Hi!
Thanks for the patch!
On Fri, 7 Feb 2014 15:59:16 +0800, Yao Qi <yao@codesourcery.com> wrote:
> * gnu-nat.c (proc_get_exception_port): Use 'lu' insetad of 'd'
> in format string.
> (proc_steal_exc_port, make_proc, inf_set_pid): Likewise.
> (inf_validate_procs, inf_signal): Likewise.
> (S_exception_raise_request): Likewise.
> (do_mach_notify_dead_name): Likewise.
> (steal_exc_port): Likewise.
> (gnu_read_inferior): Change 'copy_count''s type to
> mach_msg_type_number_t.
> (gnu_write_inferior): Likewise. Use 'lx' instead of 'x' in
> format string.
The gnu_read_inferior and gnu_write_inferior copy_count type change notes
belong to your other patch; with that changed, please push this patch.
Grüße,
Thomas
[-- Attachment #2: Type: application/pgp-signature, Size: 489 bytes --]
next prev parent reply other threads:[~2014-02-16 7:38 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 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
2014-02-07 8:01 ` [PATCH 2/3] Fix -Werror=pointer-sign warnings Yao Qi
2014-02-07 11:42 ` Joel Brobecker
2014-02-16 7:39 ` Thomas Schwinge
2014-02-17 3:32 ` 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 [this message]
2014-02-17 3:32 ` Yao Qi
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=87iosfv763.fsf@kepler.schwinge.homeip.net \
--to=thomas@codesourcery.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