mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Miles Lane <miles@megapathdsl.net>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Alan Cox <laughing@shared-source.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.10-ac11
Date: 10 Oct 2001 23:52:48 -0700	[thread overview]
Message-ID: <1002783189.1357.130.camel@stomata.megapathdsl.net> (raw)
In-Reply-To: <20011010203004.E11147@cpe-24-221-152-185.az.sprintbbd.net>
In-Reply-To: <20011011001617.A4636@lightning.swansea.linux.org.uk>  <20011010203004.E11147@cpe-24-221-152-185.az.sprintbbd.net>

On Wed, 2001-10-10 at 20:30, Tom Rini wrote:
> Hello.  In updating the PPC defconfigs, I noticed that
> drivers/usb/Config.in will ask questions on machines where CONFIG_PCI=n
> but CONFIG_EXPERIMENTAL=y.  The following puts all of the USB items
> under the if [ "$CONFIG_USB" = "y" -o "$CONFIG_USB" = "m" ] check and
> fixes some spacing bits.

Do we really still think USB deserves the Experimental label?
I use it all the time and it seems about as solid as any of
the other subsystems.  I know drivers continue to evolve, get
bugs fixed and new ones get added, but is that a good reason
to mark all USB support experimental?

Just wondering what the criteria are,

	Miles


  parent reply	other threads:[~2001-10-11  7:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-10 23:16 Alan Cox
2001-10-11  2:22 ` Matthias Andree
2001-10-11  2:59   ` Mike Fedyk
2001-10-11  4:34   ` Daniel T. Chen
2001-10-11  8:13     ` Steffen Moser
2001-10-11  2:59 ` Linux 2.4.10-ac11: swapoff frees memory + swap? Matthias Andree
2001-10-12 21:09   ` Hugh Dickins
2001-10-11  3:04 ` Linux 2.4.10-ac11 Tom Diehl
2001-10-11  3:06 ` Tom Rini
2001-10-11  3:30 ` Tom Rini
2001-10-11 22:03   ` Tom Rini
2001-10-11  6:52 ` Miles Lane [this message]
2001-10-11 15:01   ` Tom Rini

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=1002783189.1357.130.camel@stomata.megapathdsl.net \
    --to=miles@megapathdsl.net \
    --cc=laughing@shared-source.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trini@kernel.crashing.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

all inboxes | Powered by JetHome®