mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Gary Hade <garyhade@us.ibm.com>
Cc: Yinghai Lu <yhlu.kernel@gmail.com>,
	linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI: boot parameter to avoid expansion ROM memory allocation
Date: Wed, 21 May 2008 10:40:03 -0700	[thread overview]
Message-ID: <200805211040.03152.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <20080521172956.GA8024@us.ibm.com>

On Wednesday, May 21, 2008 10:29 am Gary Hade wrote:
> > > > So assuming you're ok with your last patch, I'll stuff it into
> > > > linux-next.
> > >
> > > Works for me.  Thanks.
> >
> > Ok, just pushed the norom patch to linux-next.  I'll test it out, but it
> > would be good if you could try the tree out out on one of the problem
> > machines too.
>
> Jesse, I just tried 2.6.26-rc3-next-20080521 on one of
> those systems and the pci=norom option worked as expected.

Great, thanks.  I'll push it to Linus in the next merge window.

Jesse

      reply	other threads:[~2008-05-21 17:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-12 20:57 Gary Hade
2008-05-12 21:43 ` Yinghai Lu
2008-05-12 22:30   ` Gary Hade
2008-05-13 17:48     ` Yinghai Lu
2008-05-13 21:00       ` Gary Hade
2008-05-13 21:11         ` Yinghai Lu
2008-05-13 21:44           ` Yinghai Lu
2008-05-13 22:28           ` Jesse Barnes
2008-05-13 23:23             ` Yinghai Lu
2008-05-14  0:07               ` Gary Hade
2008-05-14 16:20                 ` Gary Hade
2008-05-14 16:58                   ` [RFC] which drivers need to map ROM BARs? Jesse Barnes
2008-05-20 17:57                   ` [PATCH] PCI: boot parameter to avoid expansion ROM memory allocation Jesse Barnes
2008-05-20 20:00                     ` Gary Hade
2008-05-20 20:16                       ` Jesse Barnes
2008-05-21 17:29                         ` Gary Hade
2008-05-21 17:40                           ` Jesse Barnes [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=200805211040.03152.jbarnes@virtuousgeek.org \
    --to=jbarnes@virtuousgeek.org \
    --cc=garyhade@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=yhlu.kernel@gmail.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

all inboxes | Powered by JetHome®