From: "Kuppuswamy, Sathyanarayanan" <sathyanarayanan.kuppuswamy@linux.intel.com>
To: Bjorn Helgaas <helgaas@kernel.org>,
Hedi Berriche <hedi.berriche@hpe.com>
Cc: Ashok Raj <ashok.raj@intel.com>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Sinan Kaya <okaya@kernel.org>, Russ Anderson <rja@hpe.com>,
Joerg Roedel <jroedel@suse.com>,
stable@kernel.org, Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCH v4 1/1] PCI/ERR: don't clobber status after reset_link()
Date: Fri, 8 Jan 2021 20:04:46 -0800 [thread overview]
Message-ID: <01c316b7-afae-5ce5-0c5a-8878310fa1f6@linux.intel.com> (raw)
In-Reply-To: <20210108223043.GA1477254@bjorn-Precision-5520>
On 1/8/21 2:30 PM, Bjorn Helgaas wrote:
> Can we push this forward now? There are several pending patches in
> this area from Keith and Sathyanarayanan; I haven't gotten to them
> yet, so not sure whether they help address any of this.
Following two patches should also address the same issue.
My patch:
https://patchwork.kernel.org/project/linux-pci/patch/6f63321637fef86b6cf0beebf98b987062f9e811.1610153755.git.sathyanarayanan.kuppuswamy@linux.intel.com/
Keith's patch:
https://patchwork.kernel.org/project/linux-pci/patch/20210104230300.1277180-4-kbusch@kernel.org/
--
Sathyanarayanan Kuppuswamy
Linux Kernel Developer
next prev parent reply other threads:[~2021-01-09 4:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 15:09 [PATCH v4 0/1] PCI/ERR: fix regression introduced by 6d2c89441571 ("PCI/ERR: Update error status after reset_link()") Hedi Berriche
2020-11-02 15:09 ` [PATCH v4 1/1] PCI/ERR: don't clobber status after reset_link() Hedi Berriche
2020-11-12 15:59 ` Hedi Berriche
2020-12-10 22:41 ` Bjorn Helgaas
2021-01-08 22:30 ` Bjorn Helgaas
2021-01-09 4:04 ` Kuppuswamy, Sathyanarayanan [this message]
2021-02-08 12:33 ` Hedi Berriche
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=01c316b7-afae-5ce5-0c5a-8878310fa1f6@linux.intel.com \
--to=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=ashok.raj@intel.com \
--cc=bhelgaas@google.com \
--cc=hedi.berriche@hpe.com \
--cc=helgaas@kernel.org \
--cc=jroedel@suse.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=okaya@kernel.org \
--cc=rja@hpe.com \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).