public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>
Subject: Re: [RFC] Linux 2.6.9.1-pre1 contents
Date: Fri, 29 Oct 2004 12:33:04 +0100	[thread overview]
Message-ID: <1099049557.13082.13.camel@localhost.localdomain> (raw)
In-Reply-To: <200410282205_MC3-1-8D77-F5C5@compuserve.com>

On Gwe, 2004-10-29 at 03:02, Chuck Ebbert wrote:
> 3c59x_pci_disable_device.patch
>         Add missing pci_disable_device() in failure paths
>         NOTE: 3c59x_remove_one() needs disable call, too
>               ...as do tulip, natsemi, etc.

The mm tree with this in has shown some problems which aren't yet
fully explained and are more likely the eeprom thing.

>         Fixes from 2.6.9-ac4

I'll post -ac5 shortly although you seem to have most of that
and a lot more.

> ide_maxtor_probe.patch
>         Another Maxtor IDE drive serial number oddity

This is definitely wrong, the others look fairly sane although there are
a lot that are for such obscure cases they seem to add not reduce risk.

Alan


  parent reply	other threads:[~2004-10-29 12:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-29  2:02 [RFC] Linux 2.6.9.1-pre1 contents Chuck Ebbert
2004-10-29  7:46 ` Chris Wedgwood
2004-10-29 11:33 ` Alan Cox [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-10-29 13:27 Chuck Ebbert
2004-10-29 15:04 Chuck Ebbert
2004-10-29 14:43 ` 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=1099049557.13082.13.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=76306.1226@compuserve.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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