Re: Licensing & copyright of kernel .config files (defconfig, *config)

2014-06-01 Thread David Lang
I'm not seeing where there is a problem, unless you are trying to assume that you have no right to distribute them at all. there is no source for the .config file, it is the source. so when you distribute it, you are complying with any distribution requirements. it could be argued that

Re: Licensing & copyright of kernel .config files (defconfig, *config)

2014-06-01 Thread Robin H. Johnson
On Mon, Jun 02, 2014 at 12:01:46AM +0100, Ken Moffat wrote: > > Naively, since the defconfigs are bundled with the kernel, that could > > fall under GPLv2-only implicitly, but lacking any explicit copyright > > headers makes this interesting (arch/*/configs/* contain lots of files, > > no

Re: Licensing & copyright of kernel .config files (defconfig, *config)

2014-06-01 Thread Ken Moffat
On Sun, Jun 01, 2014 at 01:43:01AM +, Robin H. Johnson wrote: > (Please CC me on replies, not subscribed to LKML) > > Hi, > > Somewhat of an odd question, but none of the files in question seem to > have a copyright header on them... > > For a kernel .config file, either from one of the

Re: Licensing copyright of kernel .config files (defconfig, *config)

2014-06-01 Thread Ken Moffat
On Sun, Jun 01, 2014 at 01:43:01AM +, Robin H. Johnson wrote: (Please CC me on replies, not subscribed to LKML) Hi, Somewhat of an odd question, but none of the files in question seem to have a copyright header on them... For a kernel .config file, either from one of the defconfig

Re: Licensing copyright of kernel .config files (defconfig, *config)

2014-06-01 Thread Robin H. Johnson
On Mon, Jun 02, 2014 at 12:01:46AM +0100, Ken Moffat wrote: Naively, since the defconfigs are bundled with the kernel, that could fall under GPLv2-only implicitly, but lacking any explicit copyright headers makes this interesting (arch/*/configs/* contain lots of files, no copyright

Re: Licensing copyright of kernel .config files (defconfig, *config)

2014-06-01 Thread David Lang
I'm not seeing where there is a problem, unless you are trying to assume that you have no right to distribute them at all. there is no source for the .config file, it is the source. so when you distribute it, you are complying with any distribution requirements. it could be argued that

Re: Licensing & copyright of kernel .config files (defconfig, *config)

2014-05-31 Thread David Lang
I am not a Lawyer But I would start asking the same questions about these files that we ask about header files. Is there anything in the file that is not functionally required? (I believe the answer is no, everything there is required to be what it is to make the kernel work) The only

Licensing & copyright of kernel .config files (defconfig, *config)

2014-05-31 Thread Robin H. Johnson
(Please CC me on replies, not subscribed to LKML) Hi, Somewhat of an odd question, but none of the files in question seem to have a copyright header on them... For a kernel .config file, either from one of the defconfig or any other *config option that automates the answer: 1. What license does

Licensing copyright of kernel .config files (defconfig, *config)

2014-05-31 Thread Robin H. Johnson
(Please CC me on replies, not subscribed to LKML) Hi, Somewhat of an odd question, but none of the files in question seem to have a copyright header on them... For a kernel .config file, either from one of the defconfig or any other *config option that automates the answer: 1. What license does

Re: Licensing copyright of kernel .config files (defconfig, *config)

2014-05-31 Thread David Lang
I am not a Lawyer But I would start asking the same questions about these files that we ask about header files. Is there anything in the file that is not functionally required? (I believe the answer is no, everything there is required to be what it is to make the kernel work) The only