From: Paul Fulghum <paulkf@microgate.com>
To: Krzysztof Halasa <khc@pm.waw.pl>
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 12:54:42 -0600 [thread overview]
Message-ID: <4558BF72.2030408@microgate.com> (raw)
In-Reply-To: <m3ejs78adt.fsf@defiant.localdomain>
Krzysztof Halasa wrote:
> I remember something actually did "won the approval". Don't remember
> the details but I think it included conditional compilation, not
> changing CONFIG_* macros (using different name(s) instead, just not
> starting with "CONFIG_"), and IIRC no changes to Kconfigs.
It's been a while so I don't remember the details
of each suggested fix. The fixes that came closest to
being accepted changed the Kconfigs.
> At least I don't remember any objections to that last version so
> I assumed it's closed.
>
> Perhaps it was just a dream, who knows :-)
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
After a few weeks of that, I gave up.
Since the only problem is compile errors with
a broken kernel configuration, I was willing to
go with the flow and leave it in the current
functional state as it has been for years.
> 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.
But since we seem stuck in a state where real fixes
are not allowed, and this breakage is constantly reintroduced,
the best thing may be to allow the breakage and I can
provide patches to customers to get things working again.
My preference would be to either fix the warnings (which
I've tried) or leave things in a working state (which
I've also tried), but neither option seems to be allowed.
--
Paul Fulghum
Microgate Systems, Ltd.
next prev parent reply other threads:[~2006-11-13 18:56 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 [this message]
2006-11-13 20:49 ` Krzysztof Halasa
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=4558BF72.2030408@microgate.com \
--to=paulkf@microgate.com \
--cc=akpm@osdl.org \
--cc=jeff@garzik.org \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--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