mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [git pull] PCI changes for 2.6.34
Date: Sun, 28 Feb 2010 17:16:30 -0800	[thread overview]
Message-ID: <20100228171630.071840a2@infradead.org> (raw)
In-Reply-To: <4B8AF121.2060106@kernel.org>

On Sun, 28 Feb 2010 14:41:37 -0800
> 
> that trigger the reallocating...

btw we should never ever reallocate if the original layout was anywhere
near remotely sane. Doing that will cause many issues due various
craptastic bioses assuming things are where the bios put it.....
(and other operating systems also normally don't move bars etc unless
things are really b0rked)


-- 
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

      parent reply	other threads:[~2010-03-01  1:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-26 17:39 Jesse Barnes
2010-02-28 20:34 ` Linus Torvalds
2010-02-28 20:46   ` Linus Torvalds
2010-02-28 21:11     ` Yinghai
2010-02-28 21:19       ` Linus Torvalds
2010-02-28 22:41         ` Yinghai Lu
2010-02-28 23:49           ` [git pull] PCI changes for 2.6.34 - pci rom rom fail list Yinghai Lu
2010-03-01  6:28             ` Jesse Barnes
2010-03-01 16:05             ` Linus Torvalds
2010-03-01 16:35               ` Jesse Barnes
2010-03-01 17:38             ` Jesse Barnes
2010-02-28 23:51           ` [git pull] PCI changes for 2.6.34 -- pci_try_num Yinghai Lu
2010-03-01  1:16           ` Arjan van de Ven [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=20100228171630.071840a2@infradead.org \
    --to=arjan@infradead.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=yinghai@kernel.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®