From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Winkler, Tomas" <tomas.winkler@intel.com>
Cc: "Usyskin, Alexander" <alexander.usyskin@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [char-misc-next 06/12] mei: dma ring buffers allocation
Date: Wed, 12 Sep 2018 09:13:44 +0200 [thread overview]
Message-ID: <20180912071344.GB19548@kroah.com> (raw)
In-Reply-To: <5B8DA87D05A7694D9FA63FD143655C1B9D97F93D@hasmsx108.ger.corp.intel.com>
On Sun, Aug 05, 2018 at 08:38:30PM +0000, Winkler, Tomas wrote:
>
> > Subject: RE: [char-misc-next 06/12] mei: dma ring buffers allocation
> >
> >
> > > On Tue, Jul 31, 2018 at 09:35:38AM +0300, Tomas Winkler wrote:
> > > > --- /dev/null
> > > > +++ b/drivers/misc/mei/dma-ring.c
> > > > @@ -0,0 +1,103 @@
> > > > +// SPDX-License-Identifier: BSD-3-Clause OR GPL-2.0
> > >
> > > I thought Intel was not doing this type of crazy nonsense anymore and
> > > just properly creating new files that were GPL-2.0.
> > >
> > > Are you _sure_ you want to do this?
> I would prefer to keep it that way actually, hoping eventually
> relicense most of the files in the driver under the dual license,
> currently it's really kind of mix.
> I'm not sure where this was discussed before, so you've surprised me with this comment.
Please go talk to the open source legal team at Intel, this has been
discussed with them a number of times now. Look at the IB drivers for
one example of how this has changed.
thanks,
greg k-h
next prev parent reply other threads:[~2018-09-12 7:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 6:35 [char-misc-next 00/12] mei: Add DMA ring Tomas Winkler
2018-07-31 6:35 ` [char-misc-next 01/12] mei: add support for variable length mei headers Tomas Winkler
2018-07-31 6:35 ` [char-misc-next 02/12] mei: hbm: define dma ring setup protocol Tomas Winkler
2018-07-31 6:35 ` [char-misc-next 03/12] mei: hbm: introduce dma bit in the message header Tomas Winkler
2018-07-31 6:35 ` [char-misc-next 04/12] mei: restrict dma ring support to hbm version 2.1 Tomas Winkler
2018-07-31 6:35 ` [char-misc-next 05/12] mei: define dma ring buffer sizes for PCH12 HW and newer Tomas Winkler
2018-07-31 6:35 ` [char-misc-next 06/12] mei: dma ring buffers allocation Tomas Winkler
2018-08-02 8:18 ` Greg Kroah-Hartman
2018-08-02 8:20 ` Winkler, Tomas
2018-08-05 20:38 ` Winkler, Tomas
2018-09-12 7:13 ` Greg Kroah-Hartman [this message]
2018-07-31 6:35 ` [char-misc-next 07/12] mei: hbm: setup dma ring Tomas Winkler
2018-07-31 6:35 ` [char-misc-next 08/12] mei: hw: add dma ring control block Tomas Winkler
2018-07-31 6:35 ` [char-misc-next 09/12] mei: dma ring: implement rx circular buffer logic Tomas Winkler
2018-07-31 6:35 ` [char-misc-next 10/12] mei: dma ring: implement transmit flow Tomas Winkler
2018-07-31 6:35 ` [char-misc-next 11/12] mei: bump hbm version to 2.1 Tomas Winkler
2018-07-31 6:35 ` [char-misc-next 12/12] mei: me: mark CNP devices as having dma support Tomas Winkler
2018-08-02 8:19 ` [char-misc-next 00/12] mei: Add DMA ring Greg Kroah-Hartman
2018-08-08 16:11 ` Winkler, Tomas
2018-08-19 5:34 ` Winkler, Tomas
2018-08-19 6:12 ` 'Greg Kroah-Hartman'
2018-09-12 7:12 ` Greg Kroah-Hartman
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=20180912071344.GB19548@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexander.usyskin@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tomas.winkler@intel.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