From: Ilya Verbin <iverbin@gmail.com>
To: Bernd Edlinger <bernd.edlinger@hotmail.de>
Cc: Kirill Yukhin <kirill.yukhin@gmail.com>,
Andrey Turetskiy <andrey.turetskiy@intel.com>,
Jakub Jelinek <jakub@redhat.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 4/4] OpenMP 4.0 offloading to Intel MIC: non-fallback testing
Date: Fri, 21 Nov 2014 18:59:00 -0000 [thread overview]
Message-ID: <20141121184440.GA63468@msticlxl57.ims.intel.com> (raw)
In-Reply-To: <DUB118-W39F20F36D26B91274E4A4E4770@phx.gbl>
Hi,
On 21 Nov 19:19, Bernd Edlinger wrote:
> so, did you really regenerate Makefile.in in that patch, or am I missing something ?
You're right. This patch was rebased so many times, that we may forget to
regenerate it before committing.
Do you plan to submit any patch for Makefile.in?
Or should I post this change separately for review? (with regtesting)
-- Ilya
next prev parent reply other threads:[~2014-11-21 18:44 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 18:44 Bernd Edlinger
2014-11-21 18:59 ` Ilya Verbin [this message]
2014-11-21 19:01 ` Bernd Edlinger
2014-11-21 19:34 ` Ilya Verbin
2014-11-21 20:07 ` Jakub Jelinek
-- strict thread matches above, loose matches on Subject: below --
2014-10-21 17:16 [PATCH 0/4] OpenMP 4.0 offloading to Intel MIC Ilya Verbin
2014-10-30 12:45 ` [PATCH 4/4] OpenMP 4.0 offloading to Intel MIC: non-fallback testing Ilya Verbin
2014-11-06 17:55 ` Jakub Jelinek
2014-11-10 14:51 ` Ilya Verbin
2014-11-11 7:10 ` Jakub Jelinek
2014-11-12 9:18 ` Jakub Jelinek
2014-12-17 22:53 ` Thomas Schwinge
2014-12-18 10:46 ` Jakub Jelinek
2014-12-22 16:37 ` Thomas Schwinge
2014-12-18 15:56 ` Thomas Schwinge
2014-12-18 17:43 ` Ilya Verbin
2014-12-18 17:56 ` Jakub Jelinek
2014-12-22 11:49 ` Thomas Schwinge
2014-12-22 12:50 ` Jakub Jelinek
2015-01-15 19:21 ` Ilya Verbin
2015-01-15 19:25 ` Jakub Jelinek
2015-01-28 17:28 ` Ilya Verbin
2015-01-28 17:42 ` Jakub Jelinek
2015-01-28 17:51 ` Ilya Verbin
2015-02-02 14:03 ` Ilya Verbin
2014-12-26 20:53 ` Ilya Verbin
2015-01-08 16:03 ` Thomas Schwinge
2016-03-13 19:10 ` Thomas Schwinge
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=20141121184440.GA63468@msticlxl57.ims.intel.com \
--to=iverbin@gmail.com \
--cc=andrey.turetskiy@intel.com \
--cc=bernd.edlinger@hotmail.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=kirill.yukhin@gmail.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).