public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Fulghum <paulkf@microgate.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: 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:20:41 -0500	[thread overview]
Message-ID: <44876D59.1000509@microgate.com> (raw)
In-Reply-To: <20060607230202.GA12210@havoc.gtf.org>

Jeff Garzik wrote:
> On Wed, Jun 07, 2006 at 10:42:58AM -0500, Paul Fulghum wrote:
> 
>>Fix build errors caused by generic HDLC
>>and synclink configuration mismatch. Generic HDLC
>>symbols referenced from synclink drivers do not
>>resolve if synclink drivers are built-in and generic
>>HDLC is modularized.
> 
> 
> Please fix the code instead.  _No_ kernel code should be doing
> 	#define CONFIG_{xxx}
> 
> because that is a reserved namespace.

I'm happy to leave the code as is, as it has been working
for the past 8 years. I'm just trying to fix build errors
for random (unusable) kernel configs that a few people
have complained about.

Many, many people have chimed in so far without looking
at the details and I keep responding many, many, many times
that the generic HDLC support is *optional* for the synclink drivers.

So your suggestion of 'fixing' the code will *break* it.
Either unnecessary code is forced on someone, or
they are deprived of necessary code.

But OK, I'm willing to listen: how do you suggest optionally
including generic HDLC support in the synclink drivers,
depending on whether generic HDLC is enabled without
referring to a configuration option?

--
Paul


  reply	other threads:[~2006-06-08  0:20 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 [this message]
2006-06-08  0:59     ` Paul Fulghum
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=44876D59.1000509@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