public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Greg KH <greg@kroah.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
	"David S. Miller" <davem@davemloft.net>,
	linux-kernel@vger.kernel.org, linville@redhat.com
Subject: Re: pci_update_resource() getting called on sparc64
Date: Tue, 9 Aug 2005 10:54:19 +0100	[thread overview]
Message-ID: <20050809095418.GA3511@linux-mips.org> (raw)
In-Reply-To: <20050808160846.GA7710@kroah.com>

On Mon, Aug 08, 2005 at 09:08:46AM -0700, Greg KH wrote:

> {sigh}  I only pushed that one as Ralf insisted that he needed it for
> some of his hardware and that there wasn't any bad side-affects.  Ralf,
> any objections to removing this for 2.6.13?

Hmm...  I didn't see any potencial side effects.  If it causes trouble,
away with it.  The currently only affected card that I know of is the
3com 3c556B mini-PCI card.

  Ralf

      parent reply	other threads:[~2005-08-09  9:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-08 14:12 pci_update_resource() getting called on sparc64 David S. Miller
2005-08-08 14:44 ` Greg KH
2005-08-08 17:33   ` David S. Miller
2005-08-08 18:32     ` Linus Torvalds
2005-08-08 16:08       ` Greg KH
2005-08-08 19:32         ` David S. Miller
2005-08-08 19:42           ` Greg KH
2005-08-08 19:54             ` David S. Miller
2005-08-08 20:02               ` Greg KH
2005-08-08 20:19                 ` [PCI PATCH]: Make sparc64 use setup-res.c David S. Miller
2005-08-08 19:56             ` pci_update_resource() getting called on sparc64 Linus Torvalds
2005-08-08 21:38             ` John W. Linville
2005-08-08 21:43               ` David S. Miller
2005-08-08 21:59                 ` John W. Linville
2005-08-09  9:54         ` Ralf Baechle [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=20050809095418.GA3511@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=davem@davemloft.net \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linville@redhat.com \
    --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