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: <201108191104.44422.florian@openwrt.org>
Date:	Fri, 19 Aug 2011 11:04:44 +0200
From:	Florian Fainelli <florian@...nwrt.org>
To:	Luke Kenneth Casson Leighton <luke.leighton@...il.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: ARM promising platform, needs to learn from PC.

Hello,

On Friday 19 August 2011 04:02:33 Luke Kenneth Casson Leighton wrote:
> dear linus,
> 
> i've written this up, including some examples in FAQ form that would
> and would not satisfy the proposed "selfish-is-out, cooperation-is-in"
> patch-acceptance rule, here:
> http://lkcl.net/linux/linux-selfish.vs.cooperation.html
> 
> comments greatly appreciated, as would additional examples to add to the
> FAQ.

Most of your examples, especially the RDC is example is just badly chosen.

I had patches supporting this sub arch acccepted until we could get rid of it 
and make it work with the generic x86 infrastructure. The only thing that has 
not been accepted yet is some kind of "cpuid-like" feature for RDC.

The rdc321x GPIO driver has been accepted mainline and only serves on RDC-
based SoC.

Sorry to say that, but I do not understand the point of your FAQ, most people, 
if explained with good reasons, would accept a new architecture/SoC/sub-arch, 
but that's also at the price of the submitter to eventually rethink its way of 
supporting the architecture (Device Tree, code re-organisation ...).
-- 
Florian
--
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