From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: [PATCH 0/3] Factor code on suppress MI notification
Date: Mon, 27 Aug 2012 09:46:00 -0000 [thread overview]
Message-ID: <1346060757-30130-1-git-send-email-yao@codesourcery.com> (raw)
Hi,
When writing new MI notifications, I have to add 'else if (strncmp())'
stuff to suppress each new MI notification, and I don't like this way.
This patch set is to factor the code on notification suppressing.
Patch 3/3 is the major part of this set, which adds a new field
'called' in 'struct mi_cmd', and associate this field of each mi_cmd
to the flag of suppress notification we already have. It is simple
that when we want to add a new flag to suppress some notifications.
Patch 1/3 is obvious, and I'll apply it. Patch 2/3 is to define two
new macros to simply the struct initialization in array 'mi_cmds'.
Regression tested on x86_64-linux with native and gdbserver. OK to
apply?
next reply other threads:[~2012-08-27 9:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-27 9:46 Yao Qi [this message]
2012-08-27 9:46 ` [PATCH 3/3] suppress notification Yao Qi
2012-08-27 20:20 ` Tom Tromey
2012-08-27 21:01 ` Vladimir Prus
2012-08-28 2:06 ` Tom Tromey
2012-08-28 4:50 ` Vladimir Prus
2012-08-28 7:58 ` Yao Qi
2012-08-28 11:57 ` Vladimir Prus
2012-08-28 13:09 ` Yao Qi
2012-08-28 13:40 ` Pedro Alves
2012-08-28 13:50 ` Yao Qi
2012-08-28 14:09 ` Pedro Alves
2012-08-31 8:07 ` Yao Qi
2012-08-31 8:22 ` Vladimir Prus
2012-08-31 8:49 ` [committed]: " Yao Qi
2012-08-27 9:46 ` [PATCH 2/3] new macro DEF_MI_CMD_CLI and DEF_MI_CMD_MI Yao Qi
2012-08-27 20:18 ` Tom Tromey
2012-08-27 9:46 ` [PATCH 1/3] add static to mi_cmds 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=1346060757-30130-1-git-send-email-yao@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@sourceware.org \
/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