linux-kernel - Re: [PATCH] staging: vc04_services: remove unused functions

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: <1486518191.2883.2.camel@crowfest.net>
Date:   Tue, 07 Feb 2017 17:43:11 -0800
From:   Michael Zoran <mzoran@...wfest.net>
To:     Dan Carpenter <dan.carpenter@...cle.com>,
        Eric Anholt <eric@...olt.net>
Cc:     Alexander Alemayhu <alexander@...mayhu.com>,
        devel@...verdev.osuosl.org, stefan.wahren@...e.com,
        daniels@...labora.com, swarren@...dotorg.org,
        gregkh@...uxfoundation.org, lee@...nel.org,
        linux-kernel@...r.kernel.org, linux-rpi-kernel@...ts.infradead.org,
        popcornmix@...il.com, shorne@...il.com,
        linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] staging: vc04_services: remove unused functions

On Wed, 2017-02-08 at 01:19 +0300, Dan Carpenter wrote:
> On Tue, Feb 07, 2017 at 01:13:34PM -0800, Eric Anholt wrote:
> > Dan Carpenter <dan.carpenter@...cle.com> writes:
> > 
> > > There is a bunch of vc04_services that we're still looking to
> > > merge in
> > > the near future.  Please hold off deleting these until we are
> > > further
> > > along on that.
> > 
> > Checking the downstream tree, these are actually dead.
> 
> Ahh...  Thanks.  In that case, of course, fine let's remove them.
> 
> regards,
> dan carpenter
> 

I made a table awhile ago as to which entry points are being used by
what.  Most of the entry points are indeed only being used by those
other drivers which exist mostly to support a debugging tool called
vcdbg(which I didn't find that useful).

The other drivers are small drivers, but I'm not sure bringing them
here makes much sense either especially since they are mostly to
support that debugging tool.  Which complicates things because probably
half the driver could be otherwise deleted instantly.

I attached a list of driver exports and which drivers are using them.

View attachment "exports.txt" of type "text/plain" (3144 bytes)