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: Tue, 14 Nov 2006 00:05:28 +0100 [thread overview]
Message-ID: <m3psbr54nb.fsf@defiant.localdomain> (raw)
In-Reply-To: <4558E652.1080905@microgate.com> (Paul Fulghum's message of "Mon, 13 Nov 2006 15:40:34 -0600")
Paul Fulghum <paulkf@microgate.com> writes:
> To be more precise, that is many distinct
> criticisms from distinct people, some of which
> contradict each other.
That's not exactly how I remember it.
See Andrew's mail http://lkml.org/lkml/2006/6/7/257. For me, your
response(s) meant the problem was solved (so it wans't a dream :-) ).
For reference, the original patch which was almost accepted was
http://lkml.org/lkml/2006/6/7/111.
Kconfig patches were clearly a dead end, Randy hadn't realized HDLC
is optional for the synclink drivers.
--
Krzysztof Halasa
next prev parent reply other threads:[~2006-11-13 23:05 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
2006-11-13 21:40 ` Paul Fulghum
2006-11-13 23:05 ` Krzysztof Halasa [this message]
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=m3psbr54nb.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 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.