From: Paul Fulghum <paulkf@microgate.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: "Toralf Förster" <toralf.foerster@gmx.de>,
khc@pm.waw.pl, 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 09:37:25 -0600 [thread overview]
Message-ID: <45589135.9000905@microgate.com> (raw)
In-Reply-To: <45588BF0.3000100@garzik.org>
Jeff Garzik wrote:
> Unless someone fixes it The Right Way, my patch seems like the best we
> can do. People who complain "you must be able to build without hdlc"
> should step up and make it so. Currently, it is not so.
I builds just fine with and without HDLC.
The only problem is defining synclink as built in
while defining hdlc as a module.
This patch *breaks* the driver.
My previous attempts (and those of others who suggested
different fixes) at preventing this kernel
misconfiguration were all rejected. I tried
repeatedly over many weeks.
I think purposefully breaking a driver while rejecting
fixes to the real problem is a bad idea.
--
Paul Fulghum
Microgate Systems, Ltd.
next prev parent reply other threads:[~2006-11-13 15:42 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 [this message]
2006-11-13 18:33 ` Krzysztof Halasa
2006-11-13 18:54 ` Paul Fulghum
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=45589135.9000905@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 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.