public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Eric S. Raymond" <esr@thyrsus.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net
Subject: Re: [kbuild-devel] CML 1.8.4 is available
Date: Wed, 14 Nov 2001 12:33:14 -0500	[thread overview]
Message-ID: <20011114123314.A1978@thyrsus.com> (raw)
In-Reply-To: <20011113175010.A15716@thyrsus.com> <20011113182718.A1630@kroah.com> <20011114123325.A500@thyrsus.com> <20011114100020.A5287@kroah.com>
In-Reply-To: <20011114100020.A5287@kroah.com>; from greg@kroah.com on Wed, Nov 14, 2001 at 10:00:21AM -0800

Greg KH <greg@kroah.com>:
> > Historical reasons.  My rulebase was opriginally one big file for editing
> > conveniece.  What directory whould the USB serial stuff live in?
> 
> drivers/usb/serial
> 
> > > There doesn't seem to be any rules set up for drivers/hotplug.
> > 
> > What symbols should be in there,
> 
> CONFIG_HOTPLUG_PCI
> CONFIG_HOTPLUG_PCI_COMPAQ
> CONFIG_HOTPLUG_PCI_COMPAQ_NVRAM
> 
> See the Config.in file in that directory for the dependencies they have
> on each other.

OK, this wiull be in 1.8.6.  I'm going to have to figure out why my coverage 
tools didn't catch those three symbols.
-- 
		<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>

Where rights secured by the Constitution are involved, there can be no
rule making or legislation which would abrogate them.
        -- Miranda vs. Arizona, 384 US 436 p. 491

  reply	other threads:[~2001-11-14 17:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-13 22:50 CML 1.8.4 is available Eric S. Raymond
2001-11-14  2:27 ` [kbuild-devel] " Greg KH
2001-11-14 17:33   ` Eric S. Raymond
2001-11-14 18:00     ` Greg KH
2001-11-14 17:33       ` Eric S. Raymond [this message]
2001-11-14 18:57         ` Greg KH

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=20011114123314.A1978@thyrsus.com \
    --to=esr@thyrsus.com \
    --cc=greg@kroah.com \
    --cc=kbuild-devel@lists.sourceforge.net \
    --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