public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Natarajan, Kavitha" <Kavitha.Natarajan@amd.com>
To: Nick Clifton <nickc@redhat.com>,
	"binutils@sourceware.org" <binutils@sourceware.org>
Cc: "George, Jini Susan" <JiniSusan.George@amd.com>
Subject: RE: [PATCH] Binutils support for DWARF-5 DW_OP_addrx
Date: Thu, 28 Apr 2022 10:19:17 +0000	[thread overview]
Message-ID: <DM4PR12MB579656DF4530F7F754397822F7FD9@DM4PR12MB5796.namprd12.prod.outlook.com> (raw)
In-Reply-To: <c4be0bb5-1dd6-5e48-0585-50e3b83e35fb@redhat.com>

[AMD Official Use Only - General]

HI Nick,

I have resent the email after remove the label. Thanks for pointing this out.

Regards,
Kavitha

> -----Original Message-----
> From: Nick Clifton <nickc@redhat.com>
> Sent: Thursday, April 28, 2022 3:24 PM
> To: Natarajan, Kavitha <Kavitha.Natarajan@amd.com>;
> binutils@sourceware.org
> Cc: George, Jini Susan <JiniSusan.George@amd.com>
> Subject: Re: [PATCH] Binutils support for DWARF-5 DW_OP_addrx
>
> [CAUTION: External Email]
>
> Hi Natarajan,
>
> > [AMD Official Use Only - General]
>
> I know that this is terribly nit-picking, but please could you resend your
> email, but without the limitation above ?  Given that the Binutils project is
> not an AMD project I would hate for complications to arise because of that
> disclaimer.
>
> Cheers
>    Nick


  reply	other threads:[~2022-04-28 10:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-27 10:33 Natarajan, Kavitha
2022-04-28  9:54 ` Nick Clifton
2022-04-28 10:19   ` Natarajan, Kavitha [this message]
2022-04-28 10:14 Natarajan, Kavitha
2022-04-29 14:21 ` Nick Clifton
2022-05-20 10:38   ` Natarajan, Kavitha
2022-05-25 15:13     ` Nick Clifton
2022-05-25 23:42       ` Alan Modra
2022-05-26  4:35         ` Natarajan, Kavitha
2022-05-26  7:19         ` Luis Machado
2022-05-26  8:04           ` Alan Modra
2022-05-26  8:06             ` Luis Machado

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=DM4PR12MB579656DF4530F7F754397822F7FD9@DM4PR12MB5796.namprd12.prod.outlook.com \
    --to=kavitha.natarajan@amd.com \
    --cc=JiniSusan.George@amd.com \
    --cc=binutils@sourceware.org \
    --cc=nickc@redhat.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).