From: David Miller <davem@davemloft.net>
To: Yuval.Mintz@qlogic.com
Cc: netdev@vger.kernel.org, Ariel.Elior@qlogic.com
Subject: Re: [RFC net-next 01/10] qed: Add module with basic common support
Date: Thu, 10 Sep 2015 10:10:57 -0700 (PDT) [thread overview]
Message-ID: <20150910.101057.1870095895052608803.davem@davemloft.net> (raw)
In-Reply-To: <1441893261-6222-2-git-send-email-Yuval.Mintz@qlogic.com>
From: Yuval Mintz <Yuval.Mintz@qlogic.com>
Date: Thu, 10 Sep 2015 16:54:12 +0300
> Documentation/networking/LICENSE.qlogic | 288 ++
I do not want to get into the habit of having to add copy after copy
of the GPL v2 to the source tree, so this is rather inappropriate.
Everything said in that file is explicitly covered by the top-level
COPYING file.
next prev parent reply other threads:[~2015-09-10 17:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1441893261-6222-1-git-send-email-Yuval.Mintz@qlogic.com>
2015-09-10 13:54 ` [RFC net-next 01/10] qed: Add module with basic common support Yuval Mintz
2015-09-10 17:10 ` David Miller [this message]
2015-09-16 5:53 ` FW: " Yuval Mintz
2015-09-10 13:54 ` [RFC net-next 02/10] qed: Add basic L2 interface Yuval Mintz
2015-09-10 13:54 ` [RFC net-next 03/10] qede: Add basic Network driver Yuval Mintz
2015-09-10 13:54 ` [RFC net-next 04/10] qed: Add slowpath L2 support Yuval Mintz
2015-09-10 13:54 ` [RFC net-next 05/10] qede: Add basic network device support Yuval Mintz
2015-09-10 13:54 ` [RFC net-next 06/10] qede: classification configuration Yuval Mintz
2015-09-10 13:54 ` [RFC net-next 07/10] qed: Add link support Yuval Mintz
2015-09-10 13:54 ` [RFC net-next 08/10] qede: Add support for link Yuval Mintz
2015-09-10 13:54 ` [RFC net-next 09/10] qed: Add statistics support Yuval Mintz
2015-09-10 13:54 ` [RFC net-next 10/10] qede: Add basic ethtool support Yuval Mintz
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=20150910.101057.1870095895052608803.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Ariel.Elior@qlogic.com \
--cc=Yuval.Mintz@qlogic.com \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).