From: Bjorn Helgaas <helgaas@kernel.org>
To: Sean V Kelley <sean.v.kelley@intel.com>
Cc: bhelgaas@google.com, Jonathan.Cameron@huawei.com,
rjw@rjwysocki.net, ashok.raj@intel.com, tony.luck@intel.com,
sathyanarayanan.kuppuswamy@linux.intel.com, qiuxu.zhuo@intel.com,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V4 00/10] Add RCEC handling to PCI/AER
Date: Thu, 17 Sep 2020 12:36:00 -0500 [thread overview]
Message-ID: <20200917173600.GA1706067@bjorn-Precision-5520> (raw)
In-Reply-To: <20200917162548.2079894-1-sean.v.kelley@intel.com>
On Thu, Sep 17, 2020 at 09:25:38AM -0700, Sean V Kelley wrote:
> Changes since v3 [1]:
This series claims "V4 00/10", i.e., there should be this cover letter
plus 10 patches, but I only got 3 patches. I don't know if some got
lost, or if only those 3 patches were updated, or what? If it's the
latter, it's too hard for me to collect the right versions of
everything into a single series.
Either way, can you resend the entire series as a V5?
Bjorn
next prev parent reply other threads:[~2020-09-17 17:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 16:25 Sean V Kelley
2020-09-17 16:25 ` [PATCH v4 01/10] PCI/RCEC: Add RCEC class code and extended capability Sean V Kelley
2020-09-17 16:25 ` [PATCH v4 03/10] PCI/RCEC: Cache RCEC capabilities in pci_init_capabilities() Sean V Kelley
2020-09-17 16:25 ` [PATCH v4 05/10] PCI/AER: Apply function level reset to RCiEP on fatal error Sean V Kelley
2020-09-17 16:25 ` [PATCH v4 07/10] PCI/RCEC: Add RCiEP's linked RCEC to AER/ERR Sean V Kelley
2020-09-17 16:25 ` [PATCH v4 09/10] PCI/PME: Add pcie_walk_rcec() to RCEC PME handling Sean V Kelley
2020-09-17 17:36 ` Bjorn Helgaas [this message]
2020-09-17 17:55 ` [PATCH V4 00/10] Add RCEC handling to PCI/AER Sean V Kelley
2020-09-18 8:44 ` Jonathan Cameron
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=20200917173600.GA1706067@bjorn-Precision-5520 \
--to=helgaas@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=ashok.raj@intel.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=qiuxu.zhuo@intel.com \
--cc=rjw@rjwysocki.net \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=sean.v.kelley@intel.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
all inboxes | Powered by JetHome®