public inbox for linux-pci@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: Shiju Jose <shiju.jose@huawei.com>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"rjw@rjwysocki.net" <rjw@rjwysocki.net>,
	"bp@alien8.de" <bp@alien8.de>,
	"james.morse@arm.com" <james.morse@arm.com>,
	"robh@kernel.org" <robh@kernel.org>,
	"lenb@kernel.org" <lenb@kernel.org>,
	"tony.luck@intel.com" <tony.luck@intel.com>,
	"dan.carpenter@oracle.com" <dan.carpenter@oracle.com>,
	"andriy.shevchenko@linux.intel.com" 
	<andriy.shevchenko@linux.intel.com>,
	Linuxarm <linuxarm@huawei.com>
Subject: Re: [PATCH v15 0/2] ACPI / APEI: Add support to notify the vendor specific HW errors
Date: Tue, 15 Sep 2020 13:17:51 -0500	[thread overview]
Message-ID: <20200915181751.GA1408867@bjorn-Precision-5520> (raw)
In-Reply-To: <CAJZ5v0goduHVhXdOjDu6WBnD8eBYzRWAD1PO8KjabpyiHuJ1qw@mail.gmail.com>

On Tue, Sep 15, 2020 at 07:31:50PM +0200, Rafael J. Wysocki wrote:
> On Mon, Sep 14, 2020 at 2:34 PM Shiju Jose <shiju.jose@huawei.com> wrote:
> >
> > Hello,
> >
> > Can you help to merge this series?
> 
> Do you want this series to go in through the ACPI tree?

It crosses ACPI and vendor-specific PCI, but the bulk of the changes
are in PCI.  I gave some comments on the design and acked the PCI part
from my point of view.  I envisioned Lorenzo merging it since he takes
care of drivers/pci/controller/*, but either that (given your ack for
the ACPI part) or ACPI would be OK with me.

> > > drivers/acpi/apei/ghes.c                 |  63 +++++
> > > drivers/pci/controller/Kconfig           |   7 +
> > > drivers/pci/controller/Makefile          |   1 +
> > > drivers/pci/controller/pcie-hisi-error.c | 327 +++++++++++++++++++++++
> > > include/acpi/ghes.h                      |  18 ++
> > > 5 files changed, 416 insertions(+)
> > > create mode 100644 drivers/pci/controller/pcie-hisi-error.c

  reply	other threads:[~2020-09-15 18:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-03 12:34 [PATCH v15 0/2] ACPI / APEI: Add support to notify the vendor specific HW errors Shiju Jose
2020-09-03 12:34 ` [PATCH v15 1/2] ACPI / APEI: Add a notifier chain for unknown (vendor) CPER records Shiju Jose
2020-09-03 12:34 ` [PATCH v15 2/2] PCI: hip: Add handling of HiSilicon HIP PCIe controller errors Shiju Jose
2020-09-14 12:13 ` [PATCH v15 0/2] ACPI / APEI: Add support to notify the vendor specific HW errors Shiju Jose
2020-09-15 17:31   ` Rafael J. Wysocki
2020-09-15 18:17     ` Bjorn Helgaas [this message]
2020-09-15 19:10       ` Rafael J. Wysocki
2020-09-16  9:51 ` Lorenzo Pieralisi

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=20200915181751.GA1408867@bjorn-Precision-5520 \
    --to=helgaas@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=dan.carpenter@oracle.com \
    --cc=james.morse@arm.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=rafael@kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=robh@kernel.org \
    --cc=shiju.jose@huawei.com \
    --cc=tony.luck@intel.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