Searched hist:e361a772ffcd33675ffdd4637eea98a460dfed1b (Results 1 – 7 of 7) sorted by relevance
/openbmc/qemu/include/crypto/ |
H A D | afsplit.h | diff e361a772ffcd33675ffdd4637eea98a460dfed1b Wed Jan 23 08:51:23 CST 2019 Thomas Huth <thuth@redhat.com> Don't talk about the LGPL if the file is licensed under the GPL
Some files claim that the code is licensed under the GPL, but then suddenly suggest that the user should have a look at the LGPL. That's of course non-sense, replace it with the correct GPL wording instead.
Signed-off-by: Thomas Huth <thuth@redhat.com> Message-Id: <1548255083-8190-1-git-send-email-thuth@redhat.com> Reviewed-by: Laurent Vivier <laurent@vivier.eu> Signed-off-by: Laurent Vivier <laurent@vivier.eu>
|
/openbmc/qemu/crypto/ |
H A D | afsplit.c | diff e361a772ffcd33675ffdd4637eea98a460dfed1b Wed Jan 23 08:51:23 CST 2019 Thomas Huth <thuth@redhat.com> Don't talk about the LGPL if the file is licensed under the GPL
Some files claim that the code is licensed under the GPL, but then suddenly suggest that the user should have a look at the LGPL. That's of course non-sense, replace it with the correct GPL wording instead.
Signed-off-by: Thomas Huth <thuth@redhat.com> Message-Id: <1548255083-8190-1-git-send-email-thuth@redhat.com> Reviewed-by: Laurent Vivier <laurent@vivier.eu> Signed-off-by: Laurent Vivier <laurent@vivier.eu>
|
/openbmc/qemu/util/ |
H A D | range.c | diff e361a772ffcd33675ffdd4637eea98a460dfed1b Wed Jan 23 08:51:23 CST 2019 Thomas Huth <thuth@redhat.com> Don't talk about the LGPL if the file is licensed under the GPL
Some files claim that the code is licensed under the GPL, but then suddenly suggest that the user should have a look at the LGPL. That's of course non-sense, replace it with the correct GPL wording instead.
Signed-off-by: Thomas Huth <thuth@redhat.com> Message-Id: <1548255083-8190-1-git-send-email-thuth@redhat.com> Reviewed-by: Laurent Vivier <laurent@vivier.eu> Signed-off-by: Laurent Vivier <laurent@vivier.eu>
|
/openbmc/qemu/include/hw/pci-host/ |
H A D | gpex.h | diff e361a772ffcd33675ffdd4637eea98a460dfed1b Wed Jan 23 08:51:23 CST 2019 Thomas Huth <thuth@redhat.com> Don't talk about the LGPL if the file is licensed under the GPL
Some files claim that the code is licensed under the GPL, but then suddenly suggest that the user should have a look at the LGPL. That's of course non-sense, replace it with the correct GPL wording instead.
Signed-off-by: Thomas Huth <thuth@redhat.com> Message-Id: <1548255083-8190-1-git-send-email-thuth@redhat.com> Reviewed-by: Laurent Vivier <laurent@vivier.eu> Signed-off-by: Laurent Vivier <laurent@vivier.eu>
|
H A D | q35.h | diff e361a772ffcd33675ffdd4637eea98a460dfed1b Wed Jan 23 08:51:23 CST 2019 Thomas Huth <thuth@redhat.com> Don't talk about the LGPL if the file is licensed under the GPL
Some files claim that the code is licensed under the GPL, but then suddenly suggest that the user should have a look at the LGPL. That's of course non-sense, replace it with the correct GPL wording instead.
Signed-off-by: Thomas Huth <thuth@redhat.com> Message-Id: <1548255083-8190-1-git-send-email-thuth@redhat.com> Reviewed-by: Laurent Vivier <laurent@vivier.eu> Signed-off-by: Laurent Vivier <laurent@vivier.eu>
|
/openbmc/qemu/include/qemu/ |
H A D | range.h | diff e361a772ffcd33675ffdd4637eea98a460dfed1b Wed Jan 23 08:51:23 CST 2019 Thomas Huth <thuth@redhat.com> Don't talk about the LGPL if the file is licensed under the GPL
Some files claim that the code is licensed under the GPL, but then suddenly suggest that the user should have a look at the LGPL. That's of course non-sense, replace it with the correct GPL wording instead.
Signed-off-by: Thomas Huth <thuth@redhat.com> Message-Id: <1548255083-8190-1-git-send-email-thuth@redhat.com> Reviewed-by: Laurent Vivier <laurent@vivier.eu> Signed-off-by: Laurent Vivier <laurent@vivier.eu>
|
/openbmc/qemu/target/i386/hvf/ |
H A D | hvf.c | diff e361a772ffcd33675ffdd4637eea98a460dfed1b Wed Jan 23 08:51:23 CST 2019 Thomas Huth <thuth@redhat.com> Don't talk about the LGPL if the file is licensed under the GPL
Some files claim that the code is licensed under the GPL, but then suddenly suggest that the user should have a look at the LGPL. That's of course non-sense, replace it with the correct GPL wording instead.
Signed-off-by: Thomas Huth <thuth@redhat.com> Message-Id: <1548255083-8190-1-git-send-email-thuth@redhat.com> Reviewed-by: Laurent Vivier <laurent@vivier.eu> Signed-off-by: Laurent Vivier <laurent@vivier.eu>
|