public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Vladimir Mezentsev <vladimir.mezentsev@oracle.com>
To: "Cui, Lili" <lili.cui@intel.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH] gprofng: Update intel url
Date: Wed, 21 Jun 2023 10:12:16 -0700	[thread overview]
Message-ID: <a46dd289-f612-e191-c6ec-fad44f76f495@oracle.com> (raw)
In-Reply-To: <20230621072732.1652861-1-lili.cui@intel.com>

Hi Lili.

Please check it in.

Thank you for the fix gprofng.
-Vladimir




On 6/21/23 00:27, Cui, Lili wrote:
> Hi Vladimir,
>
> This patch is to update intel url, Ok for the trunk?
>
> Thanks,
> Lili
>
>
> Since the old software.intel.com has been removed, update a new one.
>
> gprofng/ChangeLog
> 2023-06-21  Lili Cui  <lili.cui@intel.com>
>
> 	* gp-display-html/gp-display-html.in: Update intel url.
> ---
>   gprofng/gp-display-html/gp-display-html.in | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/gprofng/gp-display-html/gp-display-html.in b/gprofng/gp-display-html/gp-display-html.in
> index 7ea16cf7168..dc310f836af 100644
> --- a/gprofng/gp-display-html/gp-display-html.in
> +++ b/gprofng/gp-display-html/gp-display-html.in
> @@ -5239,7 +5239,7 @@ sub generate_caller_callee
>   # Generate the html version of the disassembly file.
>   #
>   # Note to self (TBD)
> -# https://software.intel.com/content/www/us/en/develop/blogs/intel-release-new-technology-specifications-protect-rop-attacks.html
> +# https://community.intel.com/t5/Intel-oneAPI-AI-Analytics/bd-p/ai-analytics-toolkit
>   #------------------------------------------------------------------------------
>   sub generate_dis_html
>   {


      reply	other threads:[~2023-06-21 17:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-21  7:27 Cui, Lili
2023-06-21 17:12 ` Vladimir Mezentsev [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=a46dd289-f612-e191-c6ec-fad44f76f495@oracle.com \
    --to=vladimir.mezentsev@oracle.com \
    --cc=binutils@sourceware.org \
    --cc=lili.cui@intel.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).