Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Lucas Stach <l.stach@pengutronix.de>,
	Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>,
	devicetree@vger.kernel.org, linux-pci@vger.kernel.org,
	Liviu Dudau <Liviu.Dudau@arm.com>
Subject: Re: [PATCH v2] PCI: add missing DT binding for linux,pci-domain property
Date: Thu, 13 Nov 2014 19:16:14 +0100	[thread overview]
Message-ID: <1426792.5YNuomLnIU@wuerfel> (raw)
In-Reply-To: <20141113173404.GJ5064@google.com>

On Thursday 13 November 2014 10:34:04 Bjorn Helgaas wrote:
> On Thu, Nov 13, 2014 at 10:09:21AM -0700, Bjorn Helgaas wrote:
> > On Thu, Nov 06, 2014 at 04:23:20PM +0100, Lucas Stach wrote:
> > > This property was added by 41e5c0f81d3e
> > > (of/pci: Add pci_get_new_domain_nr() and of_get_pci_domain_nr())
> > > without the required binding documentation. As this property
> > > will be supported by a number of host bridge drivers going forward,
> > > add it to the common PCI binding doc.
> > > 
> > > Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
> > 
> > Applied with acks from Liviu and Rob to for-linus for v3.18, thanks a lot
> > for working this out!
> 
> Arnd, I just noticed your concern about this being linux-only.  Are you
> happy with this one?  If not, I can drop this.

If everyone else is happy with it, please keep it. We have to make
progress here eventually.

	Arnd

      reply	other threads:[~2014-11-13 18:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-06 15:23 [PATCH v2] PCI: add missing DT binding for linux,pci-domain property Lucas Stach
2014-11-06 15:40 ` Liviu Dudau
2014-11-06 19:49 ` Rob Herring
2014-11-10 14:58   ` Lucas Stach
2014-11-13 16:04     ` Rob Herring
2014-11-13 17:09 ` Bjorn Helgaas
2014-11-13 17:34   ` Bjorn Helgaas
2014-11-13 18:16     ` Arnd Bergmann [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=1426792.5YNuomLnIU@wuerfel \
    --to=arnd@arndb.de \
    --cc=Liviu.Dudau@arm.com \
    --cc=bhelgaas@google.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=l.stach@pengutronix.de \
    --cc=linux-pci@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@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