All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sinan Kaya <Okaya@kernel.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 2/2] PCI: Document ACPI description of PCI host bridges
Date: Tue, 3 Jul 2018 01:15:28 -0400	[thread overview]
Message-ID: <CAK9iUCMff7JCzRPoMnvB56D3LDFNnUwBRRBKB2xFbWkGzVQAXA@mail.gmail.com> (raw)
In-Reply-To: <153030406630.57832.11564334393458981467.stgit@bhelgaas-glaptop.roam.corp.google.com>

[-- Attachment #1: Type: text/plain, Size: 379 bytes --]

On Friday, June 29, 2018, Bjorn Helgaas <helgaas@kernel.org> wrote:

> From: Bjorn Helgaas <bhelgaas@google.com>
>
> Add a writeup about how PCI host bridges should be described in ACPI
> using PNP0A03/PNP0A08 devices, PNP0C02 devices, and the MCFG table.
>
> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
> ---


One more time.

 Reviewed-by: Sinan Kaya <okaya@kernel.org>

[-- Attachment #2: Type: text/html, Size: 770 bytes --]

  parent reply	other threads:[~2018-07-03  5:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-29 20:27 [PATCH v1 0/2] PCI: Add patch submission and ACPI FW/OS info Bjorn Helgaas
2018-06-29 20:27 ` [PATCH v1 1/2] PCI: Document patch submission hints Bjorn Helgaas
2018-06-29 22:26   ` Lukas Wunner
2018-07-01 17:45   ` Lukas Wunner
2018-07-12 15:59     ` Bjorn Helgaas
2018-07-30 14:31       ` Lukas Wunner
2018-07-30 21:56         ` Bjorn Helgaas
2018-06-29 20:27 ` [PATCH v1 2/2] PCI: Document ACPI description of PCI host bridges Bjorn Helgaas
2018-07-03  4:56   ` Sinan Kaya
2018-07-03  5:15   ` Sinan Kaya [this message]
2018-07-04  9:40   ` Rafael J. Wysocki
2018-07-04  9:40     ` Rafael J. Wysocki
2018-07-27 21:01     ` Bjorn Helgaas

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=CAK9iUCMff7JCzRPoMnvB56D3LDFNnUwBRRBKB2xFbWkGzVQAXA@mail.gmail.com \
    --to=okaya@kernel.org \
    --cc=helgaas@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@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.