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:	Mon, 22 Sep 2014 11:53:28 -0500
From:	Kim Phillips <kim.phillips@...escale.com>
To:	"J. German Rivera" <German.Rivera@...escale.com>
CC:	<gregkh@...uxfoundation.org>, <arnd@...db.de>,
	<linux-kernel@...r.kernel.org>, <stuart.yoder@...escale.com>,
	<scottwood@...escale.com>, <agraf@...e.de>,
	<linuxppc-release@...ux.freescale.net>
Subject: Re: [PATCH 0/3 v2] drivers/bus: Freescale Management Complex bus
 driver patch series

On Fri, 19 Sep 2014 17:49:38 -0500
"J. German Rivera" <German.Rivera@...escale.com> wrote:

> CHANGE HISTORY
> 
> Issues pending resolution not addressed by v2:
> - What to do with Doxygen comments in patch 1

It's clear they should be removed.

> - Whether to move or not FSL-specific header files added in include/linux,
>   by this patch series, to another location

there wasn't a valid objection against moving them under fsl/ and
changing them to use dashes instead of underscores, was there?

> - Whether to change or not the wording of the licenses used in some
>   source files

I agree with Alex to use the existing kernel versions, to be on
the safe side, but IANAL - did you want to go to the source of the
change (presumably a lawyer?) and find out why the contributors
clause was omitted and how they think that's appropriate in an
upstream submission?  If not, please resubmit after converting all
files to use the existing common kernel license text.

Thanks,

Kim
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists