linux-kernel - RE: [char-misc-next 06/12] mei: dma ring buffers allocation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Sun, 5 Aug 2018 20:38:30 +0000
From:   "Winkler, Tomas" <tomas.winkler@...el.com>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC:     "Usyskin, Alexander" <alexander.usyskin@...el.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [char-misc-next 06/12] mei: dma ring buffers allocation


> 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.
There is no hidden agenda behind this move, just let the BSD and virtualization world look at the code more freely we have quite a gap there.

Thanks
Tomas