linux-kernel - Re: drm/msm/mdp5: undefined CONFIG_MSM_BUS

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: <CAF6AEGtUVPAwxXxQ-XAFrMp=HpwVPkyVgCGQgHW6Q_6jKH8tdg@mail.gmail.com>
Date:	Thu, 9 Apr 2015 14:54:29 -0400
From:	Rob Clark <robdclark@...il.com>
To:	Paul Bolle <pebolle@...cali.nl>
Cc:	Greg KH <gregkh@...uxfoundation.org>,
	Valentin Rothberg <valentinrothberg@...il.com>,
	Hai Li <hali@...eaurora.org>,
	"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	David Airlie <airlied@...ux.ie>, rupran@...server.de,
	stefan.hengelein@....de
Subject: Re: drm/msm/mdp5: undefined CONFIG_MSM_BUS_SCALING

On Thu, Apr 9, 2015 at 2:12 PM, Paul Bolle <pebolle@...cali.nl> wrote:
> On Thu, 2015-04-09 at 19:07 +0200, Greg KH wrote:
>> I really don't understand.  Why is this code in the kernel tree if it
>> can't be built?  How does anyone use this?  By taking it and copying it
>> where?  If it can't be built, and no one can update it, and of course
>> not run it, why is it here?  What good is this code doing sitting here?
>
> The Erlangen bot (courtesy of Valentin, Stefan, and Andreas) has taken
> over what I've been doing for quite some time, but doing it much more
> thoroughly. And my experience tells me that the reports they'll send in
> will trigger more discussions like this one.
>
> A lesson I learned from my daily checks for Kconfig oddities is that
> people go to great lengths defending unbuildable code. (Do a web search
> for ATHEROS_AR231X to find a discussion that dragged on for over three
> years!) Personally I stopped caring after someone insisted on having a
> file in the tree that was in no way connected to the build system: not a
> single line in any of the Makefiles pointed at it. So, as far as I'm
> concerned, if people can't point at a patch pending, somehow, somewhere,
> that would make their code buildable one might as well delete the code.
>
> I really think it's as simple as that.
>

In the example you reference, sure it is as simple as that.  But here
we are not talking about files that aren't even referenced by build
system.  We are talking about a driver which does build and run on
upstream kernel, and which has a few small #ifdef blocks to simplify
backporting to downstream kernels (which we still do need to use for
some generations and some devices)

Sure, I'd love never to have to deal with a downstream kernel.  But
really.. I didn't create the downstream mess in the arm/android
ecosystem, I'm just trying to cope with it as best as possible.. don't
hate the player, hate the game :-P

BR,
-R

>
> Paul Bolle
>
--
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/