public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Mike Maslenkin" <mike.maslenkin@gmail.com>
To: "Chang, Abner" <Abner.Chang@amd.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"nicklew@nvidia.com" <nicklew@nvidia.com>,
	 "igork@ami.com" <igork@ami.com>
Subject: Re: [edk2-devel] [edk2-redfish-client][PATCH v2 0/3] change method for provisioning + minor fixes
Date: Tue, 19 Dec 2023 05:39:42 +0300	[thread overview]
Message-ID: <CAL77WPCwAS4D9aSx==pJw57hn-tZ7_Y=ynLtSQ7ZPdV6oi=XYg@mail.gmail.com> (raw)
In-Reply-To: <MN2PR12MB3966B1427CEF6F86EBB64367EA97A@MN2PR12MB3966.namprd12.prod.outlook.com>

Hi Abner,

Ok. I've already done it. But copyright change mentioned is for
another patchset to edk2's RedfishPkg.
Whereas you mentioned  FIRST - LAST, would you like me to add
copyrights for these changes?
I guess LAST is not required for the new added code.
I didn't add any copyrights previously,  so for my case it would be:
Copyright (c)  2023, Contributor <Contributor's email > <BR>
in any place.

Regard,
Mike.



On Tue, Dec 19, 2023 at 5:04 AM Chang, Abner <Abner.Chang@amd.com> wrote:
>
> [AMD Official Use Only - General]
>
> Hi Mike,
> According the conversation I had with Rebecca, please update your copyright that follow below format on the later patches you send; as you use the individual contributor copyright.
>
> Copyright (c) FIRST - LAST, Contributor <Contributor's email > <BR>
>
> Thanks
> Abner
>
> > -----Original Message-----
> > From: Mike Maslenkin <mike.maslenkin@gmail.com>
> > Sent: Tuesday, December 19, 2023 9:00 AM
> > To: devel@edk2.groups.io
> > Cc: Chang, Abner <Abner.Chang@amd.com>; nicklew@nvidia.com;
> > igork@ami.com; Mike Maslenkin <mike.maslenkin@gmail.com>
> > Subject: [edk2-redfish-client][PATCH v2 0/3] change method for provisioning
> > + minor fixes
> >
> > Caution: This message originated from an External Source. Use proper caution
> > when opening attachments, clicking links, or responding.
> >
> >
> > This patch set contains minor fixes.
> >
> > diff from v1:
> >  original patch 4/4 with change related to BIOS resources provisioning
> > removed.
> >
> > PR: https://github.com/tianocore/edk2-redfish-client/pull/64
> >
> > Cc: Abner Chang <abner.chang@amd.com>
> > Cc: Igor Kulchytskyy <igork@ami.com>
> > Cc: Nickle Wang <nicklew@nvidia.com>
> > Signed-off-by: Mike Maslenkin <mike.maslenkin@gmail.com>
>


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#112666): https://edk2.groups.io/g/devel/message/112666
Mute This Topic: https://groups.io/mt/103255134/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



  reply	other threads:[~2023-12-19  2:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-19  1:00 [edk2-devel] [edk2-redfish-client][PATCH v2 0/3] change method for provisioning + minor fixes Mike Maslenkin
2023-12-19  1:00 ` [edk2-devel] [edk2-redfish-client][PATCH v2 1/3] RedfishClientPkg: add check for NULL pointer to avoid ASSERT Mike Maslenkin
2023-12-19  3:40   ` Chang, Abner via groups.io
2023-12-19  1:00 ` [edk2-devel] [edk2-redfish-client][PATCH v2 2/3] RedfishClientPkg: fix typo in EfiRestJsonStructureProtocolIsReady Mike Maslenkin
2023-12-19  3:40   ` Chang, Abner via groups.io
2023-12-19  1:00 ` [edk2-devel] [edk2-redfish-client][PATCH v2 3/3] RedfishClientPkg: fix access to unitialized variable Mike Maslenkin
2023-12-19  3:40   ` Chang, Abner via groups.io
2023-12-19  2:04 ` [edk2-devel] [edk2-redfish-client][PATCH v2 0/3] change method for provisioning + minor fixes Chang, Abner via groups.io
2023-12-19  2:39   ` Mike Maslenkin [this message]
2023-12-19  3:38     ` Chang, Abner via groups.io
2024-01-03  8:33 ` Chang, Abner via groups.io

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-list 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='CAL77WPCwAS4D9aSx==pJw57hn-tZ7_Y=ynLtSQ7ZPdV6oi=XYg@mail.gmail.com' \
    --to=devel@edk2.groups.io \
    /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