From: Andi Kleen <ak@linux.intel.com>
To: Eugene Rozenfeld <Eugene.Rozenfeld@microsoft.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
"mliska@suse.cz" <mliska@suse.cz>
Subject: Re: [PATCH] gcov-profile/71672 Fix indirect call inlining with AutoFDO
Date: Fri, 30 Jul 2021 09:00:43 -0700 [thread overview]
Message-ID: <ee017bb6-73f0-89c7-03c3-bd5189b6b73d@linux.intel.com> (raw)
In-Reply-To: <MWHPR21MB07980AE38E390DE3FE9881AA91EC9@MWHPR21MB0798.namprd21.prod.outlook.com>
On 7/30/2021 12:08 AM, Eugene Rozenfeld wrote:
> This patch has the following changes:
Great thanks. Thanks for working on this. Looks all good to me (except I
guess the patches could be split up for commit)
-Andi
next prev parent reply other threads:[~2021-07-30 16:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 7:08 Eugene Rozenfeld
2021-07-30 16:00 ` Andi Kleen [this message]
2021-08-02 9:56 ` Richard Biener
2021-08-03 21:41 ` [EXTERNAL] " Eugene Rozenfeld
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=ee017bb6-73f0-89c7-03c3-bd5189b6b73d@linux.intel.com \
--to=ak@linux.intel.com \
--cc=Eugene.Rozenfeld@microsoft.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mliska@suse.cz \
/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).