From: "Venkatesh, Supreeth" <Supreeth.Venkatesh@amd.com>
To: Andrew Geissler <geissonator@gmail.com>
Cc: "manager@lfprojects.org" <manager@lfprojects.org>,
"Kumar, Ashok2" <Ashok2.Kumar@amd.com>,
"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
"Rathinasabapathi,
Rajaganesh" <Rajaganesh.Rathinasabapathi@amd.com>,
Brad Bishop <bradleyb@fuzziesquirrel.com>,
"Stephens, Christie" <Christie.Stephens@amd.com>,
"Othayoth, Jayanth" <Jayanth.Othayoth@amd.com>,
"Dhandapani, Abinaya" <Abinaya.Dhandapani@amd.com>,
"Dolaty, Mohsen" <Mohsen.Dolaty@amd.com>,
"Kurapati, Mahesh" <Mahesh.Kurapati@amd.com>
Subject: RE: AMD's Signed CCLA
Date: Thu, 16 Nov 2023 16:01:17 +0000 [thread overview]
Message-ID: <SN6PR12MB4752D0A4EE4A1C243687D14896B0A@SN6PR12MB4752.namprd12.prod.outlook.com> (raw)
In-Reply-To: <01C3FAAD-B348-4D95-BC44-E75AFF49C62F@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2341 bytes --]
[AMD Official Use Only - General]
Thank you Andrew.
Supreeth Venkatesh
System Manageability Architect | AMD
Server Software
[cid:image001.png@01DA1873.D691DC80]
From: Andrew Geissler <geissonator@gmail.com>
Sent: Thursday, November 16, 2023 8:46 AM
To: Venkatesh, Supreeth <Supreeth.Venkatesh@amd.com>
Cc: Brad Bishop <bradleyb@fuzziesquirrel.com>; openbmc@lists.ozlabs.org; manager@lfprojects.org; Dhandapani, Abinaya <Abinaya.Dhandapani@amd.com>; Dolaty, Mohsen <Mohsen.Dolaty@amd.com>; Kumar, Ashok2 <Ashok2.Kumar@amd.com>; Kurapati, Mahesh <Mahesh.Kurapati@amd.com>; Rathinasabapathi, Rajaganesh <Rajaganesh.Rathinasabapathi@amd.com>; Stephens, Christie <Christie.Stephens@amd.com>; Othayoth, Jayanth <Jayanth.Othayoth@amd.com>
Subject: Re: AMD's Signed CCLA
Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
On Nov 15, 2023, at 1:57 PM, Venkatesh, Supreeth <Supreeth.Venkatesh@amd.com<mailto:Supreeth.Venkatesh@amd.com>> wrote:
[AMD Official Use Only - General]
Please find the updated Schedule A attached.
Updated CCLA necessitated because of both CLA Manager change and Schedule A change.
Hi Supreeth,
CCLA accepted and gerrit group updated with everyone on the CLA who has logged into gerrit.
https://gerrit.openbmc.org/admin/groups/b6f229c0f3e9a11b814e6ccf56281d4064d4da4e,members
Andrew
-----Original Message-----
From: Brad Bishop <bradleyb@fuzziesquirrel.com<mailto:bradleyb@fuzziesquirrel.com>>
Sent: Thursday, August 25, 2022 8:06 AM
To: Venkatesh, Supreeth <Supreeth.Venkatesh@amd.com<mailto:Supreeth.Venkatesh@amd.com>>; 'openbmc@lists.ozlabs.org' <openbmc@lists.ozlabs.org<mailto:openbmc@lists.ozlabs.org>>; 'manager@lfprojects.org' <manager@lfprojects.org<mailto:manager@lfprojects.org>>
Cc: Spottswood, Jason <Jason.Spottswood@amd.com<mailto:Jason.Spottswood@amd.com>>
Subject: Re: AMD's Signed CCLA
[CAUTION: External Email]
On Wed, 2022-08-24 at 19:25 +0000, Venkatesh, Supreeth wrote:
[AMD Official Use Only - General]
Please find the updated signed CCLA from AMD attached.
Updated CCLA necessitated because of both CLA Manager change and
Schedule A change.
Hi Supreeth
CCLA accepted.
Thanks,
Brad
<OpenBMC.CCLA_ScheduleA_update11_15_2023.pdf>
[-- Attachment #1.2: Type: text/html, Size: 7357 bytes --]
[-- Attachment #2: image001.png --]
[-- Type: image/png, Size: 3608 bytes --]
prev parent reply other threads:[~2023-11-16 16:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 14:36 AMD's Signed CCLA Venkatesh, Supreeth
2020-06-10 14:51 ` krtaylor
2020-06-11 20:27 ` Mike Dolan
2020-06-11 21:39 ` Venkatesh, Supreeth
2020-06-12 11:54 ` Brad Bishop
2020-06-12 13:32 ` Venkatesh, Supreeth
2022-08-24 19:25 ` Venkatesh, Supreeth
2022-08-25 13:06 ` Brad Bishop
2023-11-15 19:57 ` Venkatesh, Supreeth
2023-11-16 14:46 ` Andrew Geissler
2023-11-16 16:01 ` Venkatesh, Supreeth [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=SN6PR12MB4752D0A4EE4A1C243687D14896B0A@SN6PR12MB4752.namprd12.prod.outlook.com \
--to=supreeth.venkatesh@amd.com \
--cc=Abinaya.Dhandapani@amd.com \
--cc=Ashok2.Kumar@amd.com \
--cc=Christie.Stephens@amd.com \
--cc=Jayanth.Othayoth@amd.com \
--cc=Mahesh.Kurapati@amd.com \
--cc=Mohsen.Dolaty@amd.com \
--cc=Rajaganesh.Rathinasabapathi@amd.com \
--cc=bradleyb@fuzziesquirrel.com \
--cc=geissonator@gmail.com \
--cc=manager@lfprojects.org \
--cc=openbmc@lists.ozlabs.org \
/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).