From: Paul Fulghum <paulkf@microgate.com>
To: Paul Fulghum <paulkf@microgate.com>
Cc: Jeff Garzik <jeff@garzik.org>, Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fix generic HDLC synclink mismatch build error
Date: Wed, 07 Jun 2006 19:59:05 -0500 [thread overview]
Message-ID: <44877659.2020103@microgate.com> (raw)
In-Reply-To: <44876D59.1000509@microgate.com>
Andrew:
Maybe you can lend some insight on what I should do.
I have posted multiple, working patches to correct
the build errors resultsing from random kernel configs.
But we appear to be in perpetual micromanagement by committee
mode where different people are giving conflicting
feedback of the "that's ugly" or "you shouldn't do that" kind.
I'm happy to accept any *patch* anyone wants to post
that corrects the build errors *and* does not break
the driver by removing the ability to optionally include
generic HDLC support in the synclink drivers *and*
is accepted by everyone here. Nothing that meets
those requirements has been posted yet.
(Randy's last patch comes as close as my last patch, but
Jeff says any code using conditional configuration is wrong
so that removes any patch posted so far)
I'm also happy to accept the status quo, the
driver works fine.
So where do we go from here?
--
Paul
next prev parent reply other threads:[~2006-06-08 0:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-07 15:42 [PATCH] fix generic HDLC synclink mismatch build error Paul Fulghum
2006-06-07 21:31 ` Randy.Dunlap
2006-06-07 21:43 ` Paul Fulghum
2006-06-07 21:48 ` Randy.Dunlap
2006-06-07 22:00 ` Paul Fulghum
2006-06-09 15:47 ` Paul Fulghum
2006-06-09 16:00 ` Roman Zippel
2006-06-09 16:16 ` Paul Fulghum
2006-06-09 16:37 ` Roman Zippel
2006-06-09 16:44 ` Paul Fulghum
2006-06-07 22:58 ` Roman Zippel
2006-06-08 0:23 ` Paul Fulghum
2006-06-08 2:38 ` Randy.Dunlap
2006-06-07 23:02 ` Jeff Garzik
2006-06-08 0:20 ` Paul Fulghum
2006-06-08 0:59 ` Paul Fulghum [this message]
2006-06-08 1:28 ` Andrew Morton
2006-06-08 1:52 ` Paul Fulghum
2006-06-08 13:20 ` Paul Fulghum
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=44877659.2020103@microgate.com \
--to=paulkf@microgate.com \
--cc=akpm@osdl.org \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox