linux-kernel - Re: getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

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:	Wed, 5 Jun 2013 17:35:53 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Luke Kenneth Casson Leighton <lkcl@...l.net>
Cc:	Tomasz Figa <tomasz.figa@...il.com>,
	linux-arm-kernel@...ts.infradead.org,
	"jonsmirl@...il.com" <jonsmirl@...il.com>,
	devicetree-discuss <devicetree-discuss@...abs.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	debian-arm@...ts.debian.org,
	Linux on small ARM machines 
	<arm-netbook@...ts.phcomp.co.uk>, debian-kernel@...ts.debian.org
Subject: Re: getting allwinner SoC support upstream (was Re: Uploading linux
 (3.9.4-1))

On Wed, Jun 05, 2013 at 11:56:43PM +0100, Luke Kenneth Casson Leighton wrote:
> so there's a lot of factors which i believe the linux kernel
> developers are not aware of, and haven't taken into account, and to
> place blame onto the SoC vendors for not working with *you* when *you*
> haven't made an effort to understand their situation is, i feel, not
> really helping anyone.  not that i'm one to talk about understanding
> people, but hey... :)

Wait, everyone in the world knows where we (Linux kernel developers)
are, and how to contact us, how are we supposed to know we are supposed
to go after these various companies and contact them directly?

So this SoC vendor doesn't want to merge their code upstream, fine, we
(kernel community) don't really care, and it's obvious the company
doesn't care, so what really is the issue here?

Eventually, the SoC will realize that they do need to get their code
merged, and we will still be here, as we aren't going anywhere.  At that
point in time, we will be glad to review patches and code like we do
every day for all of the thousands of other companies we deal with on a
weekly basis.

I don't see the problem here, do you?

greg k-h
--
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/