From: Bjorn Helgaas <helgaas@kernel.org>
To: Keith Busch <keith.busch@intel.com>
Cc: Linux PCI <linux-pci@vger.kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Oza Pawandeep <poza@codeaurora.org>,
Sinan Kaya <okaya@codeaurora.org>
Subject: Re: [PATCHv2 0/7] DPC updates
Date: Tue, 19 Jun 2018 16:31:22 -0500 [thread overview]
Message-ID: <20180619213121.GB33049@bhelgaas-glaptop.roam.corp.google.com> (raw)
In-Reply-To: <20180402162203.3370-1-keith.busch@intel.com>
On Mon, Apr 02, 2018 at 10:21:56AM -0600, Keith Busch wrote:
> I am terribly sorry about the delay getting this back to you. I had some
> scheduling issues with test equipment and other unrelated conflicts.
>
> I added Oza's legacy IRQ fix into this series, as I didn't see this
> staged yet, and it really does fix some issues as well as provide the
> means to clean up other parts.
>
> I'm sending this later than I intended, but hoping you might see a way
> to including this to 4.17. I can rebase to 'next' where the file is
> renamed to 'dpc.c'.
>
> Keith Busch (6):
> PCI/DPC: Enable ERR_COR
> PCI/DPC: Leave interrupts enabled while handling event
> PCI/DPC: Defer event handling to work queue
> PCI/DPC: Remove rp_pio_status from dpc struct
> PCI/AER: API for obtaining AER information
> PCI/DPC: Print AER status in DPC event handling
>
> Oza Pawandeep (1):
> PCI/DPC: Fix PCI legacy interrupt acknowledgement
>
> drivers/pci/pcie/aer/aerdrv.h | 1 +
> drivers/pci/pcie/aer/aerdrv_core.c | 8 +--
> drivers/pci/pcie/pcie-dpc.c | 106 +++++++++++++++++--------------------
> include/uapi/linux/pci_regs.h | 1 +
> 4 files changed, 55 insertions(+), 61 deletions(-)
Hi Keith, I'm sorry, with the exception of Oza's patch, I didn't get
these applied, and now they don't apply cleanly. Would you mind
rebasing them to v4.18-rc1?
Bjorn
prev parent reply other threads:[~2018-06-19 21:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-02 16:21 [PATCHv2 0/7] DPC updates Keith Busch
2018-04-02 16:21 ` [PATCHv2 1/7] PCI/DPC: Enable ERR_COR Keith Busch
2018-04-02 21:23 ` Bjorn Helgaas
2018-04-02 23:09 ` Keith Busch
2018-04-03 14:16 ` Bjorn Helgaas
2018-04-03 14:31 ` Rafael J. Wysocki
2018-04-03 14:37 ` Keith Busch
2018-04-02 16:21 ` [PATCHv2 2/7] PCI/DPC: Fix PCI legacy interrupt acknowledgement Keith Busch
2018-04-03 20:38 ` Bjorn Helgaas
2018-04-03 23:04 ` Bjorn Helgaas
2018-04-04 8:13 ` Thomas Gleixner
2018-04-04 8:38 ` Lukas Wunner
2018-04-26 5:33 ` poza
2018-05-16 15:16 ` Timur Tabi
2018-05-16 21:04 ` Bjorn Helgaas
2018-04-02 16:21 ` [PATCHv2 3/7] PCI/DPC: Leave interrupts enabled while handling event Keith Busch
2018-04-02 16:22 ` [PATCHv2 4/7] PCI/DPC: Defer event handling to work queue Keith Busch
2018-04-02 16:22 ` [PATCHv2 5/7] PCI/DPC: Remove rp_pio_status from dpc struct Keith Busch
2018-04-02 16:22 ` [PATCHv2 6/7] PCI/AER: API for obtaining AER information Keith Busch
2018-04-09 10:03 ` David Laight
2018-04-09 14:37 ` Keith Busch
2018-04-02 16:22 ` [PATCHv2 7/7] PCI/DPC: Print AER status in DPC event handling Keith Busch
2018-05-17 15:02 ` poza
2018-05-17 15:04 ` poza
2018-06-19 21:31 ` Bjorn Helgaas [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=20180619213121.GB33049@bhelgaas-glaptop.roam.corp.google.com \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=keith.busch@intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=okaya@codeaurora.org \
--cc=poza@codeaurora.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;
as well as URLs for NNTP newsgroup(s).