From: Leon Romanovsky <leonro-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: Nicolas Morey-Chaisemartin
<NMoreyChaisemartin-l3A5Bk7waGM@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
zoharb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org
Subject: Re: perftest proprietary files
Date: Sun, 23 Jul 2017 08:27:29 +0300 [thread overview]
Message-ID: <20170723052729.GC3259@mtr-leonro.local> (raw)
In-Reply-To: <2411a5c0-84f8-124e-83ce-1ee587dcf4ce-l3A5Bk7waGM@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 750 bytes --]
On Fri, Jul 21, 2017 at 10:29:11AM +0200, Nicolas Morey-Chaisemartin wrote:
> 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)
Thank you for letting us know.
Let's take it offline.
>
> Nicolas
>
> --
> 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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-07-23 5:27 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 [this message]
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
[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=20170723052729.GC3259@mtr-leonro.local \
--to=leonro-vpraknaxozvwk0htik3j/w@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