linux-kernel - Re: [GIT PULL] Staging/IIO driver patches for 4.9-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]

Message-ID: <CA+55aFx05yr20pyU47d_v-ydfzRgM3=Kt0DAaoA=6zTYznSTqQ@mail.gmail.com>
Date:   Wed, 5 Oct 2016 09:32:01 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Greg KH <gregkh@...uxfoundation.org>
Cc:     Andrew Morton <akpm@...ux-foundation.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Driver Project <devel@...uxdriverproject.org>
Subject: Re: [GIT PULL] Staging/IIO driver patches for 4.9-rc1

On Wed, Oct 5, 2016 at 12:22 AM, Greg KH <gregkh@...uxfoundation.org> wrote:
>
> Here is the big staging and IIO driver pull request for 4.9-rc1.
>
> There are a lot of patches in here, the majority due to the
> drivers/staging/greybus/ subsystem being merged in with full development
> history that went back a few years, in order to preserve the work that
> those developers did over time.  This was done the same way that btrfs
> was merged into the tree, so all should be ok there.

So I certainly have nothing against merging the development history
this way - as you say we've done this before.

However, before I pull this, I do want to understand why pulling it
makes sense in the first place.

I realize that people (very much including you personally) have spent
lots of effort on greybus, but excuse my somewhat indelicate question:
is there any *point* to merging greybus support?

Is anything ever going to use it? With project Ara being dead, where
else would you find users? Please fill me in on details - at the very
least, even if there realyl *are* good reasons to merge it, that's the
kind of information that should go into the pull request and into the
merge message.

                      Linus