bartekkuncer edited a comment on issue #19427:
URL: 
https://github.com/apache/incubator-mxnet/issues/19427#issuecomment-717949127


   @szha @PatricZhao 
   
   For mkldnn we have:
   _12. 3rdparty/mkldnn - For details, see, 3rdparty/mkldnn/LICENSE
             Copyright 2016-2019 Intel Corporation
             Copyright 2018 YANDEX LLC_
   which is consistent with their LICENSE file, but there is also:
   "Copyright 2020 Arm Limited and affiliates." in blas.cmake and .drone.yml 
files;
   "Copyright 2020 Intel Corporation" and "Copyright 2016/7/8/9-2020 Intel 
Corporation" in many mkldnn files
   
   For its submodules:
   _2. gtest - For details, see, 3rdparty/mkldnn/tests/gtests/gtest/LICENSE
            Copyright 2005-2008, Google Inc._
   where there is also "Copyright 2015, Google Inc." listed in 
mkldnn/THIRD-PARTY-PROGRAMS
   
   _9. CMake FindCUDAToolkit.cmake, FindOpenCL.cmake - For details, see,
            cmake/upstream/FindCUDAToolkit.cmake
            cmake/upstream/select_compute_arch.cmake
            3rdparty/mkldnn/cmake/FindOpenCL.cmake
            Copyright 2000-2019 Kitware, Inc. and Contributors_
   where there is also "Copyright 2000-2020 Kitware, Inc. and Contributors"
   
   _19. Benchdnn - For details, see 3rdparty/mkldnn/tests/benchdnn/README.md
             Copyright 2017-2018 Intel Corporation_
   where there is "Copyright 2017-2020 Intel Corporation" in benchdnn files
   
   Not listed in our license but listed in mkldnn/THIRD-PARTY-PROGRAMS:
   Boost C++ Libraries:
   Copyright 2005-2014 Daniel James.
   Should it be added or is this one unnecessary?


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to