From: DJ Delorie <dj@redhat.com>
To: Sebastian Perta <Sebastian.Perta@renesas.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] rl78 adddi3 improvement
Date: Sat, 14 Oct 2017 08:39:00 -0000 [thread overview]
Message-ID: <xnr2u65zyl.fsf@greed.delorie.com> (raw)
In-Reply-To: <HK2PR0601MB1828F479D671327E4B67CFC0E08C0@HK2PR0601MB1828.apcprd06.prod.outlook.com> (message from Sebastian Perta on Mon, 14 Aug 2017 14:25:52 +0000)
Sebastian Perta <Sebastian.Perta@renesas.com> writes:
> Please let me know if this is OK, Thank you!
Sorry for the delay, it's OK and I committed it for you with a few minor
changes to make it work with today's tree.
Thanks!
prev parent reply other threads:[~2017-10-14 0:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-14 15:56 Sebastian Perta
2017-10-14 8:39 ` DJ Delorie [this message]
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=xnr2u65zyl.fsf@greed.delorie.com \
--to=dj@redhat.com \
--cc=Sebastian.Perta@renesas.com \
--cc=gcc-patches@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).