From: David Miller <davem@davemloft.net>
To: sarveshwar.bandi@emulex.com
Cc: netdev@vger.kernel.org, vasundhara.volam@emulex.com
Subject: Re: [PATCH v2 net-next 1/2] be2net: Modify GPL Marking in all source files.
Date: Wed, 23 Jan 2013 02:06:18 -0500 (EST) [thread overview]
Message-ID: <20130123.020618.638425092581514860.davem@davemloft.net> (raw)
In-Reply-To: <c09a42d1-150f-4d78-b2c4-2bedec3bd577@CMEXHTCAS2.ad.emulex.com>
From: <sarveshwar.bandi@emulex.com>
Date: Wed, 23 Jan 2013 12:22:03 +0530
> From: Vasundhara Volam <vasundhara.volam@emulex.com>
>
> The following modifications have been made to copyright:
> - years of copyright extended to include 2013
> - specify EMULEX and SLI as trademarks of Emulex corporation
> - specify emulex website
> - Added a more detailed disclaimer " ALL EXPRESS OR IMPLIED CONDITIONS,
> REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF
> MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT,
> ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO
> BE LEGALLY INVALID."
>
> Signed-off-by: Vasundhara Volam <vasundhara.volam@emulex.com>
> Signed-off-by: Sarveshwar Bandi <sarveshwar.bandi@emulex.com>
You're just essentially reading the contents of the patch, that's
not satisfactory.
In particular, the problem is that you aren't explaining why you're
making all of these changes.
There needs to be justification for copyright changes like this,
you are not providing them.
next prev parent reply other threads:[~2013-01-23 7:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 6:52 [PATCH v2 net-next 1/2] be2net: Modify GPL Marking in all source files sarveshwar.bandi
2013-01-23 7:06 ` David Miller [this message]
2013-01-23 7:28 ` Bandi,Sarveshwar
2013-01-23 19:37 ` Bandi,Sarveshwar
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=20130123.020618.638425092581514860.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=sarveshwar.bandi@emulex.com \
--cc=vasundhara.volam@emulex.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 NNTP newsgroup(s).