From: Ingo Molnar <mingo@elte.hu>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Stephen Hemminger <shemminger@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Roman Zippel <zippel@linux-m68k.org>,
Jan Engelhardt <jengelh@gmx.de>,
Richard Purdie <rpurdie@rpsys.net>,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [patch, -git] input: CONFIG_INPUT_APANEL build fix
Date: Wed, 30 Apr 2008 23:20:29 +0200 [thread overview]
Message-ID: <20080430212029.GA28813@elte.hu> (raw)
In-Reply-To: <20080430163924.ZZRA012@mailhub.coreip.homeip.net>
* Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:
> I thought the many years old rule for Linux kernel is to fix the
> issues properly and not turn kernel into patchwork of crappy code.
correct, except if that would mean breakage for users.
> If we want to fix the randconfi issue I'd rather revert commit
> 66242f7ec531953fbc2f4040c5ffe1f1ffe6c5c9 for now (they only thing it
> did was beautify menuconfig look) and wait for Kconfig to be fixed. It
> is not driver's task to track through all dependencies.
yep ... just dont export our internal crappiness to testers and users.
i'm not suggesting this is your fault in any way - but nevertheless many
other subsystems have to deal with the same Kconfig issues and they
manage to limp along.
Ingo
next prev parent reply other threads:[~2008-04-30 21:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 18:54 [patch, -git] input: CONFIG_INPUT_APANEL build fix Ingo Molnar
2008-04-30 19:04 ` Dmitry Torokhov
2008-04-30 20:20 ` Ingo Molnar
2008-04-30 20:56 ` Roman Zippel
2008-04-30 22:21 ` Dmitry Torokhov
2008-04-30 21:00 ` Dmitry Torokhov
2008-04-30 21:20 ` Ingo Molnar [this message]
2008-04-30 22:26 ` Dmitry Torokhov
2008-04-30 22:38 ` Ingo Molnar
2008-04-30 22:47 ` Dmitry Torokhov
2008-05-01 0:51 ` Roman Zippel
2008-05-01 2:36 ` Dmitry Torokhov
2008-05-01 6:25 ` Jan Engelhardt
2008-05-01 1:29 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080430212029.GA28813@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=dmitry.torokhov@gmail.com \
--cc=jengelh@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rpurdie@rpsys.net \
--cc=sam@ravnborg.org \
--cc=shemminger@linux-foundation.org \
--cc=zippel@linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.