public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Miles Lane <miles@megapathdsl.net>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Russell King <rmk@arm.linux.org.uk>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.0-test12-pre7
Date: Thu, 07 Dec 2000 11:11:22 -0800	[thread overview]
Message-ID: <3A2FE0DA.5080100@megapathdsl.net> (raw)
In-Reply-To: <Pine.LNX.4.10.10012070923210.2370-100000@penguin.transmeta.com>

Linus Torvalds wrote:

> probably vote for getting rid of the device enables in
> pci_assign_unassigned_resources() (for all the reasons already mentioned
> by others - scribbling over memory due to not being quiescent etc). But
> it's not worth breaking now. 2.5.x material. Most PCI drivers may already
> do the right thing, but I bet that the USB driver wasn't the only one who
> forgot..

Is anyone compiling these change lists for 2.5?  I seem to see a few
of these ideas mentioned on LKML each week.  It would be nice to not
have these ideas fade away.

	Miles

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-12-07 19:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.10.10012061618300.2415-100000@penguin.transmeta.com>
2000-12-07  1:29 ` 2.4.0-test12-pre7 Linus Torvalds
2000-12-07 14:11   ` 2.4.0-test12-pre7 Russell King
2000-12-07 17:34     ` 2.4.0-test12-pre7 Linus Torvalds
2000-12-07 19:11       ` Miles Lane [this message]
2000-12-07 19:01     ` 2.4.0-test12-pre7 Kai Germaschewski
2000-12-07 21:37       ` 2.4.0-test12-pre7 Tom Rini
2000-12-08 17:08   ` 2.4.0-test12-pre7 [ymfpci doesn't survive suspend to disk] Simon Huggins
2000-12-08 17:22     ` Alan Cox

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=3A2FE0DA.5080100@megapathdsl.net \
    --to=miles@megapathdsl.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    --cc=torvalds@transmeta.com \
    /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