linux-kernel - Re: [GIT PULL] Staging driver patches for 3.19-rc1

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:	Tue, 16 Dec 2014 10:35:47 +0100
From:	Richard Weinberger <richard@....at>
To:	Greg KH <gregkh@...uxfoundation.org>,
	Christoph Hellwig <hch@...radead.org>
CC:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>
Subject: Re: [GIT PULL] Staging driver patches for 3.19-rc1

Am 15.12.2014 um 19:56 schrieb Greg KH:
> On Mon, Dec 15, 2014 at 10:41:03AM -0800, Greg KH wrote:
>> On Mon, Dec 15, 2014 at 10:39:15AM -0800, Christoph Hellwig wrote:
>>> On Mon, Dec 15, 2014 at 07:23:35PM +0100, Richard Weinberger wrote:
>>>> I don't understand this kind of logic.
>>>> a) Binder is considered a piece of shite.
>>>> b) Google is working on a (hopefully sane) replacement.
>>>>
>>>> Why moving it out of staging then? What is the benefit?
>>>
>>> There is none, and Greg didn't even bother addressing the various
>>> comments when this first came up.
>>
>> I thought I did, it was a long thread at the time, and I was on the road
>> for 3 weeks, sorry if I missed something.
>>
>>> So a clear NAK from me on this one.
>>
>> You don't have to maintain it, I do, so why does it concern you?
> 
> Ok, that was a bit snotty on my part, I apologize.
> 
> But really, this is self-contained, doesn't touch any core
> infrastructure, and is really just like any other driver for hardware
> that people don't use.  It shouldn't affect anything elsewhere in the
> kernel, so objecting to it seems odd to me.

Doesn't it use internal stuff from fs/file.c?
Anyway, Linus pulled it.

I'm just a bit astonished that binder finally sneaked into the
core kernel. Hopefully no smart ass will ever decide to make
some userspace component hard depend on it...

Thanks,
//richard
--
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/