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]

Message-ID: <5B8DA87D05A7694D9FA63FD143655C1B9D97B874@hasmsx108.ger.corp.intel.com>
Date:   Thu, 2 Aug 2018 08:20:08 +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


> 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?
> 
> > +/*
> > + * Copyright(c) 2016 - 2018 Intel Corporation. All rights reserved.
> 
> How is a new file copyright 2016?  You have had this file laying around for 2
> years?
Yes, it takes time till a HW is released to public..
Tomas