From: Greg KH <gregkh@linuxfoundation.org>
To: Jon Mason <jon.mason@intel.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-pci@vger.kernel.org, Dave Jiang <dave.jiang@intel.com>
Subject: Re: [RFC v2 1/2] PCI-Express Non-Transparent Bridge Support
Date: Tue, 31 Jul 2012 16:14:31 -0700 [thread overview]
Message-ID: <20120731231431.GA1558@kroah.com> (raw)
In-Reply-To: <20120731225105.GD14080@jonmason-lab>
On Tue, Jul 31, 2012 at 03:51:05PM -0700, Jon Mason wrote:
> On Tue, Jul 31, 2012 at 03:23:38PM -0700, Greg KH wrote:
> > On Sun, Jul 29, 2012 at 05:26:33PM -0700, Jon Mason wrote:
> > > + * You should have received a copy of the GNU General Public License
> > > + * along with this program; if not, write to the Free Software
> > > + * Foundation, Inc., 51 Franklin St - Fifth Floor, Boston, MA 02110-1301 USA.
> >
> > You really are going to track the FSF's office movements for the next
> > 40+ years?
> >
> > > + * The full GNU General Public License is included in this distribution
> > > + * in the file called LICENSE.GPL.
> >
> > No it isn't, this sentance is totally wrong for any in-kernel code,
> > please remove it.
> >
> > Also do the same for all the other files you added please.
>
> I echo'ed your original comments on this to Intel Legal and am waiting
> on a response. I 100% agree, but I need their signoff first.
>
> It is worth noting that this version of the license is already in the
> kernel in numerous other drivers:
> drivers/sfi/*
> drivers/scsi/isci/*
> drivers/dma/ioat/dma_v3.c
> drivers/net/wireless/iwlwifi/*
> drivers/net/wireless/iwlegacy/*
Just because others got it wrong, doesn't mean you need to continue to :)
greg k-h
next prev parent reply other threads:[~2012-07-31 23:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-30 0:26 [RFC v2 0/2] PCI-Express Non-Transparent Bridge Support Jon Mason
2012-07-30 0:26 ` [RFC v2 1/2] " Jon Mason
2012-07-30 16:50 ` Bjorn Helgaas
2012-07-30 18:15 ` Jon Mason
2012-07-31 3:35 ` Jianbin Kang
2012-07-31 16:33 ` Jon Mason
2012-08-01 2:10 ` Jianbin Kang
2012-08-01 2:18 ` Jiang, Dave
2012-07-31 13:45 ` Bjorn Helgaas
2012-07-31 16:02 ` chetan loke
2012-07-31 17:03 ` Bjorn Helgaas
2012-07-31 17:27 ` Jon Mason
2012-07-31 18:02 ` chetan loke
2012-08-02 1:43 ` Jon Mason
2012-07-31 17:10 ` Jon Mason
2012-07-31 16:14 ` chetan loke
2012-07-31 22:23 ` Greg KH
2012-07-31 22:51 ` Jon Mason
2012-07-31 23:14 ` Greg KH [this message]
2012-07-31 22:25 ` Greg KH
2012-08-02 1:49 ` Jon Mason
2012-07-30 0:26 ` [RFC v2 2/2] net: Add support for NTB virtual ethernet device Jon Mason
2012-07-30 14:02 ` Jiri Pirko
2012-07-30 18:19 ` Jon Mason
2012-07-30 20:09 ` Jiri Pirko
2012-07-31 22:28 ` Greg KH
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=20120731231431.GA1558@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dave.jiang@intel.com \
--cc=jon.mason@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--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 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.