All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Dave Airlie <airlied@gmail.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	dri-devel@lists.sourceforge.net,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drm: Fix support for PCI domains
Date: Thu, 12 Aug 2010 17:35:26 -0700	[thread overview]
Message-ID: <20100812173526.2c002045@blake> (raw)
In-Reply-To: <AANLkTik+MX8cKz6hWyaa8Z2gK7fehXzjSPpeiyExuMjb@mail.gmail.com>

> > Hm, so pci_domain_nr should just return 0 on platforms where
> > CONFIG_PCI_DOMAINS isn't set.  I'd expect that to be the case when
> > CONFIG_PCI=n...  Maybe we just need to shuffle the definition
> > around?
> 
> I suspect something like the attached would suffice.
> 
> Or maybe moving the CONFIG_PCI_DOMAINS checkout outside CONFIG_PCI.

Yeah, that looks ok, and better than putting it in drm.  I'll apply to
my for-linus branch for the next PCI fixes pull.

Thanks,
Jesse

  reply	other threads:[~2010-08-13  0:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-06  3:55 [PATCH] drm: Fix support for PCI domains Benjamin Herrenschmidt
2010-08-06  7:11 ` Michel Dänzer
2010-08-06  7:11 ` Michel Dänzer
2010-08-12 21:30 ` Geert Uytterhoeven
2010-08-12 21:30 ` Geert Uytterhoeven
2010-08-12 23:33   ` Dave Airlie
2010-08-12 23:33   ` Dave Airlie
2010-08-12 23:45     ` Jesse Barnes
2010-08-12 23:45     ` Jesse Barnes
2010-08-13  0:22       ` Dave Airlie
2010-08-13  0:35         ` Jesse Barnes [this message]
2010-08-13  0:35         ` Jesse Barnes
2010-08-13  0:22       ` Dave Airlie
  -- strict thread matches above, loose matches on Subject: below --
2010-08-06  3:55 Benjamin Herrenschmidt

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=20100812173526.2c002045@blake \
    --to=jbarnes@virtuousgeek.org \
    --cc=airlied@gmail.com \
    --cc=benh@kernel.crashing.org \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.