public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@mandrakesoft.com>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Adrian Bunk <bunk@fs.tum.de>,
	Marcelo Tosatti <marcelo@conectiva.com.br>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.18-rc2
Date: 21 Feb 2002 13:43:29 +0100	[thread overview]
Message-ID: <m2zo232efi.fsf@localhost.mandrakesoft.com> (raw)
In-Reply-To: <Pine.NEB.4.44.0202210924450.3462-100000@mimas.fachschaften.tu-muenchen.de> <3C74BDB4.5CD92998@mandrakesoft.com>
In-Reply-To: <3C74BDB4.5CD92998@mandrakesoft.com>

>>>>> "jeff" == Jeff Garzik <jgarzik@mandrakesoft.com> writes:

jeff> Adrian Bunk wrote:
>> as discussed in the thread of your 2.4.18-rc1 announcement (see [1] and
>> [2]) 2.4.18 adds CONFIG_FB_TRIDENT but the code doesn't compile.  It's
>> IMHO not a good a idea to add a new option that doesn't compile to a
>> stable kernel. Please apply the patch below that disables this option as a
>> workaround to 2.4.18:

jeff> No -- it's already marked with CONFIG_EXPERIMENTAL.

jeff> Thus if you are compiling this software, you do so at your own risk...

Then remove the:
#error blah blah

from the source file.

Later, Juan.

-- 
In theory, practice and theory are the same, but in practice they 
are different -- Larry McVoy

      reply	other threads:[~2002-02-21 12:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-18 20:16 Linux 2.4.18-rc2 Marcelo Tosatti
2002-02-18 21:52 ` Rik van Riel
2002-02-19  1:43 ` Paul Mackerras
2002-02-21  8:29 ` Adrian Bunk
2002-02-21  9:28   ` Jeff Garzik
2002-02-21 12:43     ` Juan Quintela [this message]

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=m2zo232efi.fsf@localhost.mandrakesoft.com \
    --to=quintela@mandrakesoft.com \
    --cc=bunk@fs.tum.de \
    --cc=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@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