From: Nick Clifton <nickc@redhat.com>
To: Kazuhiro Inaoka <inaoka.kazuhiro@renesas.com>
Cc: binutils@sources.redhat.com, gdb-patches@sources.redhat.com,
cgen@sources.redhat.com
Subject: Re: [PATCH] m32r's pop need PIPE_O attribute
Date: Mon, 15 Dec 2003 12:20:00 -0000 [thread overview]
Message-ID: <m3y8tei8i2.fsf@redhat.com> (raw)
In-Reply-To: <009201c3c2c5$30ab89c0$2569910a@tool.maec.co.jp> (Kazuhiro Inaoka's message of "Mon, 15 Dec 2003 13:37:47 +0900")
Hi Kazuhiro,
> 2003-12-15 Kazuhiro Inaoka < inaoka dot kazuhiro at renesas dot com >
>
> * cpu/m32r.cpu: pop need PIPE_O attribute.
Approved and applied.
Cheers
Nick
next prev parent reply other threads:[~2003-12-15 12:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-15 4:32 Kazuhiro Inaoka
2003-12-15 12:20 ` Nick Clifton [this message]
2003-12-16 0:26 ` Kazuhiro Inaoka
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=m3y8tei8i2.fsf@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=cgen@sources.redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=inaoka.kazuhiro@renesas.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).