All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vlad Zolotarov <vladz@cloudius-systems.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] Your RETA patches to ixgbe/ixgbevf
Date: Thu, 17 Dec 2015 19:36:43 +0200	[thread overview]
Message-ID: <5672F2AB.1010909@cloudius-systems.com> (raw)
In-Reply-To: <F6FB0E698C9B3143BDF729DF2228664691E59DB8@ORSMSX116.amr.corp.intel.com>

I assign copyright back to Intel for the changes in <4ce37a4c05cfb5bfd445419d5b880a91bb19228f> <ixgbe: Add a RETA query command to VF-PF channel API>

I assign copyright back to Intel for the changes in <94cf66f87064b8e4b24412f042b98e7cba4ebce2> <ixgbevf: Add a RETA query code>


On 12/17/2015 07:14 PM, Skidmore, Donald C wrote:
> Hi Vlad,
>
> Here is the canned email I send out when asking for copyright back to Intel (which needs to be done for each patch):
>
> Some or most of your patch(es) make changes to code that we share among our other drivers so we retain copyright on certain files so that we are able to re-license the code.  With that, I ask if you can assign copyright of your changes to Intel so that we can maintain copyright on the changes.  You will still be the author, just Intel would retain copyright on the changes.
>
> All we need is a reply, stating "I assign copyright back to Intel for the changes in < 4ce37a4c05cfb5bfd445419d5b880a91bb19228f> < ixgbe: Add a RETA query command to VF-PF channel API>"
> All we need is a reply, stating "I assign copyright back to Intel for the changes in < 94cf66f87064b8e4b24412f042b98e7cba4ebce2> < ixgbevf: Add a RETA query code>"
>
> Sorry we should have asked you earlier.
> Thanks,
> -Don Skidmore <donald.c.skidmore@intel.com>


  reply	other threads:[~2015-12-17 17:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-17 17:14 [Intel-wired-lan] Your RETA patches to ixgbe/ixgbevf Skidmore, Donald C
2015-12-17 17:36 ` Vlad Zolotarov [this message]
2015-12-17 17:41   ` Skidmore, Donald C
2015-12-17 17:56     ` Vlad Zolotarov

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=5672F2AB.1010909@cloudius-systems.com \
    --to=vladz@cloudius-systems.com \
    --cc=intel-wired-lan@osuosl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.