public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: R.E.Wolff@BitWizard.nl (Rogier Wolff)
To: "Eric S. Raymond" <esr@thyrsus.com>
Cc: Richard Gooch <rgooch@atnf.csiro.au>,
	"Edward S. Marshall" <esm@logic.net>,
	Rik van Riel <riel@conectiva.com.br>,
	linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net
Subject: Re: Cross-referencing frenzy
Date: Thu, 19 Apr 2001 11:26:08 +0200 (MEST)	[thread overview]
Message-ID: <200104190926.LAA06753@cave.bitwizard.nl> (raw)
In-Reply-To: <20010419013748.C29686@thyrsus.com> from "Eric S. Raymond" at "Apr 19, 2001 01:37:48 am"

Eric S. Raymond wrote:
> Richard Gooch <rgooch@atnf.csiro.au>:
> > > Look at the filename. ;-) They're not being kept around, they just
> > > happen to be mentioned in the devfs ChangeLog, and esr's overzealous
> > > crossref tool caught them. *grin*
> 
> I've already fixed that.
>  
> > A cleaner solution is to parse the source code, ignoring comment
> > blocks. However, that's a bit more work.
> 
> Not too hard.  I think I can do that.

Eric, 

I think it should be possible to do: 

/* to enable the special stuff, change the "undef" to "define",
   If you really want you can add this to Config.in so that you're presented
   with this choice when configuring your kernel. But it's not neccesary
   for the general public to always see this toggle.  */
#undef CONFIG_SX_SPECIALSTUFF

#ifdef CONFIG_SX_SPECIALSTUFF
...

#endif


Roger. 

-- 
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* There are old pilots, and there are bold pilots. 
* There are also old, bald pilots. 

  reply	other threads:[~2001-04-19  9:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-19  3:34 Cross-referencing frenzy Eric S. Raymond
2001-04-19  4:00 ` Richard Gooch
2001-04-19  4:11   ` Rik van Riel
2001-04-19  4:36     ` Edward S. Marshall
2001-04-19  5:06       ` Richard Gooch
2001-04-19  5:37         ` Eric S. Raymond
2001-04-19  9:26           ` Rogier Wolff [this message]
2001-04-19 13:36             ` [kbuild-devel] " Eric S. Raymond
2001-04-19 15:22               ` Rogier Wolff
2001-04-19  5:38         ` Jeff Garzik
2001-04-19  5:32       ` Eric S. Raymond
2001-04-19 11:41     ` Alan Cox
2001-04-19  4:49 ` Andreas Dilger
2001-04-19 13:23   ` Mike Castle
2001-04-19 13:36     ` Alan Cox
2001-04-19 17:33   ` Eric S. Raymond
2001-04-19 20:53     ` Jim Treadway
2001-04-19  8:02 ` Russell King
2001-04-19 13:16   ` Eric S. Raymond
2001-04-19 14:17     ` Jeff Garzik
2001-04-19 14:25       ` Eric S. Raymond
2001-04-19 18:49       ` [kbuild-devel] " Peter Samuelson

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=200104190926.LAA06753@cave.bitwizard.nl \
    --to=r.e.wolff@bitwizard.nl \
    --cc=esm@logic.net \
    --cc=esr@thyrsus.com \
    --cc=kbuild-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rgooch@atnf.csiro.au \
    --cc=riel@conectiva.com.br \
    /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