From: Martin Jambor <mjambor@suse.cz>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
Cesar Philippidis <cesar@codesourcery.com>,
Alexander Monakov <amonakov@ispras.ru>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] omp-low.c split
Date: Wed, 14 Dec 2016 13:24:00 -0000 [thread overview]
Message-ID: <20161214131900.vqck67v3ofpdvsmp@virgil.suse.cz> (raw)
In-Reply-To: <87fulqsldz.fsf@hertz.schwinge.homeip.net>
Hi,
On Wed, Dec 14, 2016 at 02:14:32PM +0100, Thomas Schwinge wrote:
>
> I still couldn't allocate time to review the patch, but at least I now
> have tested it -- no regressions.
Great, thanks!
> As I suppose you want to commit this
> as sooner than later ;-) and you already have approval as I understand
> it, how about you do commit it, and I'll then later follow up, with any
> changes I'd additionally like to get done.
>
I am about to re-base, re-test, add the few formatting fixes that
Jakub suggested to the second patch and commit. Hopefully all of it
today.
Martin
next prev parent reply other threads:[~2016-12-14 13:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-09 13:08 Martin Jambor
2016-12-09 13:25 ` Alexander Monakov
2016-12-09 13:53 ` Martin Jambor
2016-12-09 14:22 ` Jakub Jelinek
2016-12-09 16:19 ` Alexander Monakov
2016-12-13 10:20 ` Martin Jambor
2016-12-13 10:16 ` Martin Jambor
2016-12-13 10:35 ` Jakub Jelinek
2016-12-14 16:56 ` Martin Jambor
2016-12-13 12:58 ` Alexander Monakov
2016-12-13 11:39 ` Thomas Schwinge
2016-12-13 11:43 ` Jakub Jelinek
2016-12-13 12:42 ` Martin Jambor
2016-12-13 14:48 ` Cesar Philippidis
2016-12-14 13:16 ` Thomas Schwinge
2016-12-14 13:24 ` Martin Jambor [this message]
2021-08-04 12:40 ` Thomas Schwinge
2021-08-04 12:45 ` Jakub Jelinek
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=20161214131900.vqck67v3ofpdvsmp@virgil.suse.cz \
--to=mjambor@suse.cz \
--cc=amonakov@ispras.ru \
--cc=cesar@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=thomas@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).