linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Guilherme G. Piccoli" <gpiccoli@canonical.com>
To: sathyanarayanan.kuppuswamy@linux.intel.com, linux-pci@vger.kernel.org
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	ashok.raj@intel.com, knsathya@kernel.org,
	Bjorn Helgaas <helgaas@kernel.org>,
	Jay Vosburgh <jay.vosburgh@canonical.com>,
	Sinan Kaya <okaya@kernel.org>,
	haifeng.zhao@intel.com, chris.newcomer@canonical.com,
	gpiccoli@canonical.com
Subject: Re: [PATCH v7 1/2] PCI/ERR: Call pci_bus_reset() before calling ->slot_reset() callback
Date: Tue, 24 Nov 2020 15:45:00 -0300	[thread overview]
Message-ID: <6349d22f-cf49-bab4-ad0f-a928e65622af@canonical.com> (raw)
In-Reply-To: 

Hi Kuppuswamy Sathyanarayanan (and all involved here), thanks for the
patch! I'd like to ask what is the status of this patchset - I just
"parachuted" in the issue, and by tracking the linux-pci ML, I found
this V7 (and all previous versions since V2). Also, noticed that Jay's
email might have gotten lost in translation (he's not CCed in latest
versions of the patchset).

I was able to find even another interesting thread that might be
related, Ethan's patchset. So, if any of the developers can clarify the
current status of this patchset or if the functionality hereby proposed
ended-up being implemented in another patch, I appreciate a lot.

Thanks in advance! Below, some references to lore archives.
Cheers,


Guilherme


References:

This V7 link:
https://lore.kernel.org/linux-pci/546d346644654915877365b19ea534378db0894d.1602788209.git.sathyanarayanan.kuppuswamy@linux.intel.com/

V6:
https://lore.kernel.org/linux-pci/546d346644654915877365b19ea534378db0894d.1602663397.git.sathyanarayanan.kuppuswamy@linux.intel.com/#t

V5:
https://lore.kernel.org/linux-pci/162495c76c391de6e021919e2b69c5cd2dbbc22a.1602632140.git.sathyanarayanan.kuppuswamy@linux.intel.com/

V4:
https://lore.kernel.org/linux-pci/5c5bca0bdb958e456176fe6ede10ba8f838fbafc.1602263264.git.sathyanarayanan.kuppuswamy@linux.intel.com/

V3:
https://lore.kernel.org/linux-pci/cbba08a5e9ca62778c8937f44eda2192a2045da7.1595617529.git.sathyanarayanan.kuppuswamy@linux.intel.com/

V2:
https://lore.kernel.org/linux-pci/ce417fbf81a8a46a89535f44b9224ee9fbb55a29.1591307288.git.sathyanarayanan.kuppuswamy@linux.intel.com/#t

Ethan's related(?) patchset, V8 :
https://lore.kernel.org/linux-pci/20201007113158.48933-1-haifeng.zhao@intel.com/#t


             reply	other threads:[~2020-11-24 18:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-24 18:45 Guilherme G. Piccoli [this message]
2020-11-24 20:43 ` [PATCH v7 1/2] PCI/ERR: Call pci_bus_reset() before calling ->slot_reset() callback Kuppuswamy, Sathyanarayanan
2020-11-27  1:47 ` Ethan Zhao
  -- strict thread matches above, loose matches on Subject: below --
2020-10-15 19:02 Kuppuswamy Sathyanarayanan
2020-10-26 19:36 ` Kuppuswamy Sathyanarayanan

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=6349d22f-cf49-bab4-ad0f-a928e65622af@canonical.com \
    --to=gpiccoli@canonical.com \
    --cc=ashok.raj@intel.com \
    --cc=chris.newcomer@canonical.com \
    --cc=haifeng.zhao@intel.com \
    --cc=helgaas@kernel.org \
    --cc=jay.vosburgh@canonical.com \
    --cc=knsathya@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=okaya@kernel.org \
    --cc=sathyanarayanan.kuppuswamy@linux.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;
as well as URLs for NNTP newsgroup(s).