linux-kernel - Re: [PATCH v2] early_printk: consolidate random copies of identical code

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: <CAP=VYLp-A9dMwD4_48zokL-XQ5pqPrkAy4UVx6cwUHQ3KozpSQ@mail.gmail.com>
Date:	Thu, 7 Mar 2013 20:15:08 -0500
From:	Paul Gortmaker <paul.gortmaker@...driver.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Mike Frysinger <vapier@...too.org>, Ingo Molnar <mingo@...nel.org>,
	Randy Dunlap <rdunlap@...radead.org>,
	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
	Russell King <linux@....linux.org.uk>,
	Michal Simek <monstr@...str.eu>,
	Ralf Baechle <ralf@...ux-mips.org>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	Paul Mundt <lethal@...ux-sh.org>,
	"David S. Miller" <davem@...emloft.net>,
	Chris Metcalf <cmetcalf@...era.com>,
	Richard Weinberger <richard@....at>
Subject: Re: [PATCH v2] early_printk: consolidate random copies of identical code

On Thu, Mar 7, 2013 at 7:56 PM, Andrew Morton <akpm@...ux-foundation.org> wrote:
> On Thu, 7 Mar 2013 19:49:35 -0500 Paul Gortmaker <paul.gortmaker@...driver.com> wrote:
>
>> > otoh, offering useless stuff to non-kernel-developers has downsides
>> > with no balancing benefit, and we really should optimise things for
>> > our users because there are so many more of them than there are of us.
>>
>> Glad to hear that, and I agree totally.  I hope the above three lines
>> will persuade people to merge practical/sane dependency lines that
>> have the end users in mind, instead of focusing on ease of local testing.
>
> It is possible to just ignore the Kconfig system and type "make
> drivers/foo/bar.o".  Sometimes this actually works.

Yes, I've used that many times too[1] -- it however fails on things like
sched which has C files including C files.  Dave Miller had posted a tip
to people a while back on how to ferret out basic compile failures without
having _any_ cross toolchains by at least doing the basic CPP part, but I
can't find the archived thread in my  rudimentary searches at the moment...

In any case, it sounds like all are in agreement that we should not
complicate the end user main Kconfig use case just to offload a trivial
component of the automated build testing burden onto general users.

[1] https://git.kernel.org/cgit/linux/kernel/git/paulg/longterm-queue-2.6.34.git/tree/scripts/buildcommits

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