linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Smith <whydoubt@yahoo.com>
To: linux-kernel@vger.kernel.org, kwall@kurtwerks.com
Subject: Re: [PATCH] 2.6.0-test1 Nonexistent Symbols During Config
Date: Thu, 17 Jul 2003 14:13:56 -0700 (PDT)	[thread overview]
Message-ID: <20030717211356.53055.qmail@web40010.mail.yahoo.com> (raw)

A few notes on each of these.  I do not offer
recommendations, only facts.

CONFIG_X86_SSE:
  Used in include/asm-i386/bugs.h to panic if
  the kernel is compiled for SSE2 but the
  processor does not support it.

CONFIG_NET_PCMCIA_RADIO:
  Used in drivers/net/wireless/ray_cs.c.

CONFIG_INTEL_RNG:
  Not used anywhere in code.

 -- Jeff Smith

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

             reply	other threads:[~2003-07-17 20:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-17 21:13 Jeff Smith [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-17  1:06 [PATCH] 2.6.0-test1 Nonexistent Symbols During Config Kurt Wall

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=20030717211356.53055.qmail@web40010.mail.yahoo.com \
    --to=whydoubt@yahoo.com \
    --cc=kwall@kurtwerks.com \
    --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;
as well as URLs for NNTP newsgroup(s).