From: Krzysztof Halasa <khc@pm.waw.pl>
To: Paul Fulghum <paulkf@microgate.com>
Cc: "Jeff Garzik" <jeff@garzik.org>,
"Toralf Förster" <toralf.foerster@gmx.de>,
linux-kernel@vger.kernel.org, "Andrew Morton" <akpm@osdl.org>
Subject: Re: [PATCH] Re: linux-2.6.19-rc5-g088406bc build #120 failed
Date: Mon, 13 Nov 2006 21:49:47 +0100 [thread overview]
Message-ID: <m3ac2v6phw.fsf@defiant.localdomain> (raw)
In-Reply-To: <4558BF72.2030408@microgate.com> (Paul Fulghum's message of "Mon, 13 Nov 2006 12:54:42 -0600")
Paul Fulghum <paulkf@microgate.com> writes:
> We were in a perpetual state of:
>
> 1. supply patch
> 2. get criticism from new person just joining thread
> 3. change patch to address criticism
> 4. goto #1
Right, the description fits. OTOH I recall the criticism had a fair
amount of merit. That's how the things work here. Been there many
times BTW.
>> Nevertheless a fix outlined above would be acceptable, wouldn't it?
>
> It breaks things by forcing the customer to include code
> that is not required. That is an issue for embedded systems.
Nope, the fix which didn't change Kconfig and just assumed HDLC=m and
SYNCLINK*=y => HDLC is not available. I.e., the one with
#if defined(CONFIG_HDLC_MODULE) &&/|| defined(CONFIG_SYNCLINK*something)
#define CONFIG_HDLC something
changed into
#if defined(CONFIG_HDLC_MODULE) &&/|| defined(CONFIG_SYNCLINK*something)
#define USE_HDLC something
^^^^^^^^
> But since we seem stuck in a state where real fixes
> are not allowed, and this breakage is constantly reintroduced,
It may look like that sometimes but it's not real. Anyway I think
everyone would benefit from the correct fix and the issue wouldn't
come again. Having looked at it I'd fix it myself but I'm pretty
sure you still have the old patch (which changes CONFIG_ macros
outside Kconfig, I mean in .c files) and it could be trivially
modified then applied (and perhaps tested with real hardware if
needed).
--
Krzysztof Halasa
next prev parent reply other threads:[~2006-11-13 20:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-13 8:43 linux-2.6.19-rc5-g088406bc build #120 failed Toralf Förster
2006-11-13 14:49 ` [PATCH] " Jeff Garzik
2006-11-13 15:00 ` Paul Fulghum
2006-11-13 15:14 ` Jeff Garzik
2006-11-13 15:37 ` Paul Fulghum
2006-11-13 18:33 ` Krzysztof Halasa
2006-11-13 18:54 ` Paul Fulghum
2006-11-13 20:49 ` Krzysztof Halasa [this message]
2006-11-13 21:40 ` Paul Fulghum
2006-11-13 23:05 ` Krzysztof Halasa
2006-11-13 23:10 ` Paul Fulghum
2006-11-14 0:07 ` Krzysztof Halasa
2006-11-14 1:08 ` Paul Fulghum
2006-11-14 14:25 ` Krzysztof Halasa
2006-11-13 23:13 ` Randy Dunlap
2006-11-13 23:06 ` Andrew Morton
2006-11-13 23:15 ` Paul Fulghum
2006-11-14 0:00 ` Daniel Barkalow
2006-11-13 21:36 ` Toralf Förster
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=m3ac2v6phw.fsf@defiant.localdomain \
--to=khc@pm.waw.pl \
--cc=akpm@osdl.org \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulkf@microgate.com \
--cc=toralf.foerster@gmx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox