From: Benjamin Drung <benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
To: Zohar Ben Aharon <zoharb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
Nicolas Morey-Chaisemartin
<NMoreyChaisemartin-l3A5Bk7waGM@public.gmane.org>,
"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: perftest proprietary files
Date: Thu, 27 Jul 2017 16:19:54 +0200 [thread overview]
Message-ID: <1501165194.4572.32.camel@profitbricks.com> (raw)
In-Reply-To: <DB6PR05MB3493378C569E416783246ED4A9BE0-HESHCvp+V+r4Tc8ENT3My9qRiQSDpxhJvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
Hi Nicolas,
can Mellanox adjust the header of the files? Currently it says:
#
# Copyright (C) Mellanox Technologies Ltd. 2001-2011. ALL RIGHTS RESERVED.
# This software product is a proprietary product of Mellanox Technologies Ltd.
# (the "Company") and all right, title, and interest and to the software product,
# including all associated intellectual property rights, are and shall
# remain exclusively with the Company.
#
# This software product is governed by the End User License Agreement
# provided with the software product.
# $COPYRIGHT$
# $HEADER$
#
but since it is gpl/bsd (as you said), the header should read something like:
# Copyright (C) Mellanox Technologies Ltd. 2001-2011. All rights
reserved.
#
# This software is available to you under a choice of one of
two
# licenses. You may choose to be licensed under the terms of the
GNU
# General Public License (GPL) Version 2, available from the file
#
COPYING in the main directory of this source tree, or the
# OpenIB.org
BSD license below:
#
# Redistribution and use in source and binary
forms, with or
# without modification, are permitted provided that
the following
# conditions are met:
#
# - Redistributions of
source code must retain the above
# copyright notice, this list
of conditions and the following
# disclaimer.
#
# -
Redistributions in binary form must reproduce the above
#
copyright notice, this list of conditions and the following
#
disclaimer in the documentation and/or other materials
# provided
with the distribution.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT
WARRANTY OF ANY KIND,
# EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
THE WARRANTIES OF
# MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE
AND
# NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
HOLDERS
# BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
IN AN
# ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR
IN
# CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
#
SOFTWARE.
Am Donnerstag, den 27.07.2017, 12:35 +0000 schrieb Zohar Ben Aharon:
> Hi Nicolas,
>
>
> I've verified your issue,
> Mellanox provide perftest to be under gpl/bsd license.
> since Mellanox is the maintainer and release perftest as an open
> source SW it still can have copyrights on each file that was written
> or approved by its developers,
> So the headers should remain and declared as Mellanox propriety.
>
> Hope is helps you.
>
> Thanks,
>
>
> Zohar Ben Aharon
> Perfromance Engineer
> Mellanox Technologies Ltd.
> Phone: +972 (74) 723 6829
> Mobile: +972 (52) 691 1115
>
>
>
>
> -----Original Message-----
> From: Zohar Ben Aharon
> Sent: Monday, July 24, 2017 8:41 AM
> To: 'Nicolas Morey-Chaisemartin' <NMoreyChaisemartin-l3A5Bk7waGM@public.gmane.org>; linux-
> rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> Subject: RE: perftest proprietary files
>
> Sorry for the late response,
> ill verify this files propriety and back to you.
>
>
> -----Original Message-----
> From: Nicolas Morey-Chaisemartin [mailto:NMoreyChaisemartin-l3A5Bk7waGM@public.gmane.org]
> Sent: Friday, July 21, 2017 11:29 AM
> To: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org; Zohar Ben Aharon <zoharb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org
> >
> Subject: perftest proprietary files
>
> Hi,
>
> While packaging perftest for SUSE, I discovered that some files have
> headers declaring the software as Mellanox proprietary while the
> COPYING declares LGPL/BSD.
>
> The files are:
> * Makefile.am
> * Makefile.in
> * configure.ac
>
> Should these headers be dropped ?
>
> (I pinged zoharb about this already without much luck. Figured it
> might be worth a shot here)
>
--
Benjamin Drung
System Developer
Debian & Ubuntu Developer
ProfitBricks GmbH
Greifswalder Str. 207
D - 10405 Berlin
Email: benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org
Web: https://www.profitbricks.com
Sitz der Gesellschaft: Berlin.
Registergericht: Amtsgericht Charlottenburg, HRB 125506B.
Geschäftsführer: Achim Weiss.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-07-27 14:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 8:29 perftest proprietary files Nicolas Morey-Chaisemartin
[not found] ` <2411a5c0-84f8-124e-83ce-1ee587dcf4ce-l3A5Bk7waGM@public.gmane.org>
2017-07-23 5:27 ` Leon Romanovsky
2017-07-24 5:41 ` Zohar Ben Aharon
2017-07-27 12:35 ` Zohar Ben Aharon
[not found] ` <DB6PR05MB3493378C569E416783246ED4A9BE0-HESHCvp+V+r4Tc8ENT3My9qRiQSDpxhJvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2017-07-27 14:19 ` Benjamin Drung [this message]
[not found] ` <1501165194.4572.32.camel-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2017-07-27 14:25 ` Zohar Ben Aharon
[not found] ` <DB6PR05MB3493CD259D663959D1D0DFA0A9BE0-HESHCvp+V+r4Tc8ENT3My9qRiQSDpxhJvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2017-07-27 15:33 ` Benjamin Drung
[not found] ` <1501169609.4572.34.camel-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2017-07-27 16:28 ` Jason Gunthorpe
[not found] ` <20170727162825.GA7364-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-07-27 16:49 ` Benjamin Drung
2017-07-27 15:33 ` Nicolas Morey-Chaisemartin
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=1501165194.4572.32.camel@profitbricks.com \
--to=benjamin.drung-eikl63zcoxah+58jc4qpia@public.gmane.org \
--cc=NMoreyChaisemartin-l3A5Bk7waGM@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=zoharb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.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