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: <1433852683.24094.8.camel@x220>
Date:	Tue, 09 Jun 2015 14:24:43 +0200
From:	Paul Bolle <pebolle@...cali.nl>
To:	monstr@...str.eu
Cc:	Julia Lawall <julia.lawall@...6.fr>,
	Kedareswara rao Appana <appana.durga.rao@...inx.com>,
	dan.j.williams@...el.com, vinod.koul@...el.com,
	michal.simek@...inx.com, soren.brinkmann@...inx.com,
	appanad@...inx.com, punnaia@...inx.com, dmaengine@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	Srikanth Thokala <sthokal@...inx.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Joe Perches <joe@...ches.com>,
	Fengguang Wu <fengguang.wu@...el.com>
Subject: Re: [PATCH v4 2/2] dma: Add Xilinx AXI Central Direct Memory Access
 Engine driver support

On Tue, 2015-06-09 at 14:12 +0200, Michal Simek wrote
> ok. Will check all our drivers we have to get it synchronized but I
> expect that a lot of drivers have problems there.

So do I. Cleaning that all up would add a lot of churn. I'm _not_
volunteering to do that.

What I decided to do was to (try to) comment on each patch that adds
another license mismatch. The idea being that this might annoy someone
into suggesting a (mostly) fool proof alternative to MODULE_LICENSE().
That didn't really work out yet (though Julia's and your response is
encouraging)

On the sunny side I note that very few new mismatches get added (at
least, I tricked myself into believing that).

Thanks,


Paul Bolle

--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ