From: Alex Michon <amichon@kalrayinc.com>
To: Christoph Hellwig <hch@lst.de>
Cc: michael haeuptle <michael.haeuptle@hpe.com>,
CS1PR8401MB07283E5AFD950C136FFC565E95C60
<CS1PR8401MB07283E5AFD950C136FFC565E95C60@cs1pr8401mb0728.namprd84.prod.outlook.com>,
dstein <dstein@hpe.com>, linux-pci <linux-pci@vger.kernel.org>,
lukas <lukas@wunner.de>
Subject: Re: Deadlock during PCIe hot remove
Date: Sun, 30 Oct 2022 09:39:33 +0100 (CET) [thread overview]
Message-ID: <496564878.633246.1667119173775.JavaMail.zimbra@kalray.eu> (raw)
In-Reply-To: <20221030082818.GB4949@lst.de>
Sorry, I wanted to reply to this thread: https://lore.kernel.org/linux-pci/CS1PR8401MB07283E5AFD950C136FFC565E95C60@CS1PR8401MB0728.NAMPRD84.PROD.OUTLOOK.COM/
but it looks like something went wrong with the email delivery.
----- Original Message -----
From: "Christoph Hellwig" <hch@lst.de>
To: "Alex Michon" <amichon@kalrayinc.com>
Cc: "michael haeuptle" <michael.haeuptle@hpe.com>, "CS1PR8401MB07283E5AFD950C136FFC565E95C60" <CS1PR8401MB07283E5AFD950C136FFC565E95C60@cs1pr8401mb0728.namprd84.prod.outlook.com>, "dstein" <dstein@hpe.com>, "hch" <hch@lst.de>, "linux-pci" <linux-pci@vger.kernel.org>, "lukas" <lukas@wunner.de>
Sent: Sunday, October 30, 2022 9:28:18 AM
Subject: Re: Deadlock during PCIe hot remove
On Wed, Oct 26, 2022 at 12:05:57PM +0200, Alex Michon wrote:
> Hello,
>
> Is there any update on this bug ?
What is "this bug"?
next prev parent reply other threads:[~2022-10-30 8:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <492110694.79456.1666778757292.JavaMail.zimbra@kalray.eu>
2022-10-30 8:28 ` Deadlock during PCIe hot remove Christoph Hellwig
2022-10-30 8:39 ` Alex Michon [this message]
2020-03-24 15:21 Haeuptle, Michael
2020-03-24 15:35 ` Hoyer, David
2020-03-24 15:37 ` Haeuptle, Michael
2020-03-24 15:39 ` Hoyer, David
2020-03-24 16:26 ` Haeuptle, Michael
2020-03-24 16:32 ` Hoyer, David
2020-03-24 16:15 ` Lukas Wunner
2020-03-25 10:40 ` Christoph Hellwig
2020-03-26 19:30 ` Haeuptle, Michael
2020-03-29 13:04 ` Lukas Wunner
2020-03-31 8:14 ` Christoph Hellwig
2020-03-29 15:43 ` Lukas Wunner
2020-03-30 16:15 ` Haeuptle, Michael
2020-03-31 13:01 ` Lukas Wunner
2020-03-31 15:02 ` Haeuptle, Michael
2020-04-02 19:24 ` Haeuptle, Michael
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=496564878.633246.1667119173775.JavaMail.zimbra@kalray.eu \
--to=amichon@kalrayinc.com \
--cc=CS1PR8401MB07283E5AFD950C136FFC565E95C60@cs1pr8401mb0728.namprd84.prod.outlook.com \
--cc=dstein@hpe.com \
--cc=hch@lst.de \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=michael.haeuptle@hpe.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).