From: Karsten Merker <karsten@excalibur.cologne.de>
To: linux-mips@linux-mips.org
Subject: Re: make xmenuconfig is broken
Date: Tue, 29 Oct 2002 20:24:36 +0100 [thread overview]
Message-ID: <20021029192436.GA1344@excalibur.cologne.de> (raw)
In-Reply-To: <20021029103545.K24266@mvista.com>
On Tue, Oct 29, 2002 at 10:35:45AM -0800, Jun Sun wrote:
> In addition, there are two SERIAL and SERIAL_CONSOLE related
> setting which should be in drivers/char/Config.in
> instead of arch/mips/config-shared.in.
>
> The following hack makes xmenuconfig work again, apparently breaking
> decstation and IP22. If nobody interested in those two machines
> move the config, I will make an attempt to do so.
Why do you want to move the config? Is there any technical reason besides
grouping the subarch specific character devices below the generic
character devices instead of having a subarch specific menu ("DECstation
character devices")?
Regards,
Karsten
--
#include <standard_disclaimer>
Nach Paragraph 28 Abs. 3 Bundesdatenschutzgesetz widerspreche ich der Nutzung
oder Uebermittlung meiner Daten fuer Werbezwecke oder fuer die Markt- oder
Meinungsforschung.
next prev parent reply other threads:[~2002-10-29 19:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-29 18:35 make xmenuconfig is broken Jun Sun
2002-10-29 19:24 ` Karsten Merker [this message]
2002-10-29 21:30 ` Jun Sun
2002-10-30 13:07 ` Maciej W. Rozycki
2002-11-07 19:26 ` Maciej W. Rozycki
2002-11-07 20:33 ` SEGEV defines Bradley Bozarth
2002-11-07 22:10 ` Daniel Jacobowitz
2002-11-07 22:23 ` make xmenuconfig is broken Jun Sun
2002-11-08 12:25 ` Maciej W. Rozycki
2002-11-08 17:35 ` Ralf Baechle
2002-11-08 18:30 ` Maciej W. Rozycki
2002-11-08 19:31 ` Ralf Baechle
2002-10-30 15:58 ` Ralf Baechle
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=20021029192436.GA1344@excalibur.cologne.de \
--to=karsten@excalibur.cologne.de \
--cc=linux-mips@linux-mips.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