From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Paul Fulghum <paulkf@microgate.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, khc@pm.waw.pl
Subject: Re: [PATCH] fix generic HDLC synclink mismatch build error
Date: Wed, 7 Jun 2006 14:48:59 -0700 [thread overview]
Message-ID: <20060607144859.3ae7bb6d.rdunlap@xenotime.net> (raw)
In-Reply-To: <4487488F.3010100@microgate.com>
On Wed, 07 Jun 2006 16:43:43 -0500 Paul Fulghum wrote:
> Randy.Dunlap wrote:
> > See my new patch below. All done in Kconfig, no
> > source file changes needed. Highly preferable. :)
>
> The effect is the exact same as mine (if there is a mismatch
> then generic HDLC support for synclink is silently disabled),
> and your patch is against a patch that has already been dropped.
>
> The only difference is the granularity of enabling
> the HDLC option for individual synclink adapter types,
> which is not really an issue (as this is not in <= 2.6.16 anyways).
>
> I'd prefer to stick with my patch as it is simpler,
> and maintains compatibility with the way thing are done
> in <= 2.6.16 (customer documentation does not need updating).
Sure, that's fine, your call.
I just wanted you to see how this is handled in some other places
in the kernel tree.
---
~Randy
next prev parent reply other threads:[~2006-06-07 21:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-07 15:42 Paul Fulghum
2006-06-07 21:31 ` Randy.Dunlap
2006-06-07 21:43 ` Paul Fulghum
2006-06-07 21:48 ` Randy.Dunlap [this message]
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
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=20060607144859.3ae7bb6d.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@osdl.org \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=paulkf@microgate.com \
/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
all inboxes | Powered by JetHome®