From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: "Bjorn Helgaas" <bhelgaas@google.com>,
"Mahesh J Salgaonkar" <mahesh@linux.ibm.com>,
"Oliver O'Halloran" <oohall@gmail.com>,
"Michael Ellerman" <mpe@ellerman.id.au>,
"Nicholas Piggin" <npiggin@gmail.com>,
"Christophe Leroy" <christophe.leroy@csgroup.eu>,
"Saeed Mahameed" <saeedm@nvidia.com>,
"Leon Romanovsky" <leon@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Alex Williamson" <alex.williamson@redhat.com>,
"Lukas Wunner" <lukas@wunner.de>,
"Mika Westerberg" <mika.westerberg@linux.intel.com>,
"Stefan Roese" <sr@denx.de>, "Jim Wilson" <wilson@tuliptree.org>,
"David Abdurachmanov" <david.abdurachmanov@gmail.com>,
"Pali Rohár" <pali@kernel.org>,
linux-pci@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-rdma@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 7/7] PCI: Work around PCIe link training failures
Date: Sun, 14 May 2023 21:54:10 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.2.21.2305142145320.11892@angie.orcam.me.uk> (raw)
In-Reply-To: <alpine.DEB.2.21.2305071922310.54316@angie.orcam.me.uk>
On Sun, 7 May 2023, Maciej W. Rozycki wrote:
> > We're going to land this series this cycle, come hell or high water.
>
> Thank you for coming back to me and for your promise. I'll strive to
> address your concerns next weekend.
>
> Unfortunately a PDU in my remote lab has botched up and I've lost control
> over it (thankfully not one for the RISC-V machine affected by the patch
> series, so I can still manage it for reboots, etc., but the botched PDU is
> actually upstream), so depending on how situation develops I may have to
> book air travel instead and spend the whole weekend getting things back to
> normal operation at my lab. That unit was not supposed to fail, not in
> such a silly way anyway, sigh...
Last Thu the situation with the PDU became critical, so I spent a better
part of yesterday and today travelling and then all night long getting
things sorted. So it'll have to be next weekend when I get back to these
patches. I hope we can still make it regardless.
Maciej
WARNING: multiple messages have this Message-ID (diff)
From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
"Eric Dumazet" <edumazet@google.com>,
"Oliver O'Halloran" <oohall@gmail.com>,
"Stefan Roese" <sr@denx.de>, "Leon Romanovsky" <leon@kernel.org>,
linux-rdma@vger.kernel.org, "Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Jim Wilson" <wilson@tuliptree.org>,
"Nicholas Piggin" <npiggin@gmail.com>,
"Alex Williamson" <alex.williamson@redhat.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Mika Westerberg" <mika.westerberg@linux.intel.com>,
"David Abdurachmanov" <david.abdurachmanov@gmail.com>,
linuxppc-dev@lists.ozlabs.org,
"Mahesh J Salgaonkar" <mahesh@linux.ibm.com>,
"David S. Miller" <davem@davemloft.net>,
"Lukas Wunner" <lukas@wunner.de>,
netdev@vger.kernel.org, "Pali Rohár" <pali@kernel.org>,
"Saeed Mahameed" <saeedm@nvidia.com>
Subject: Re: [PATCH v8 7/7] PCI: Work around PCIe link training failures
Date: Sun, 14 May 2023 21:54:10 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.2.21.2305142145320.11892@angie.orcam.me.uk> (raw)
In-Reply-To: <alpine.DEB.2.21.2305071922310.54316@angie.orcam.me.uk>
On Sun, 7 May 2023, Maciej W. Rozycki wrote:
> > We're going to land this series this cycle, come hell or high water.
>
> Thank you for coming back to me and for your promise. I'll strive to
> address your concerns next weekend.
>
> Unfortunately a PDU in my remote lab has botched up and I've lost control
> over it (thankfully not one for the RISC-V machine affected by the patch
> series, so I can still manage it for reboots, etc., but the botched PDU is
> actually upstream), so depending on how situation develops I may have to
> book air travel instead and spend the whole weekend getting things back to
> normal operation at my lab. That unit was not supposed to fail, not in
> such a silly way anyway, sigh...
Last Thu the situation with the PDU became critical, so I spent a better
part of yesterday and today travelling and then all night long getting
things sorted. So it'll have to be next weekend when I get back to these
patches. I hope we can still make it regardless.
Maciej
next prev parent reply other threads:[~2023-05-14 20:54 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 0:20 [PATCH v8 0/7] pci: Work around ASMedia ASM2824 PCIe link training failures Maciej W. Rozycki
2023-04-06 0:20 ` Maciej W. Rozycki
2023-04-06 0:21 ` [PATCH v8 1/7] PCI: pciehp: Rely on `link_active_reporting' Maciej W. Rozycki
2023-04-06 0:21 ` Maciej W. Rozycki
2023-04-06 0:21 ` [PATCH v8 2/7] PCI: Export PCI link retrain timeout Maciej W. Rozycki
2023-04-06 0:21 ` Maciej W. Rozycki
2023-05-04 22:21 ` Bjorn Helgaas
2023-05-04 22:21 ` Bjorn Helgaas
2023-04-06 0:21 ` [PATCH v8 3/7] PCI: Execute `quirk_enable_clear_retrain_link' earlier Maciej W. Rozycki
2023-04-06 0:21 ` Maciej W. Rozycki
2023-04-06 0:21 ` [PATCH v8 4/7] PCI: Initialize `link_active_reporting' earlier Maciej W. Rozycki
2023-04-06 0:21 ` Maciej W. Rozycki
2023-04-06 0:21 ` [PATCH v8 5/7] powerpc/eeh: Rely on `link_active_reporting' Maciej W. Rozycki
2023-04-06 0:21 ` Maciej W. Rozycki
2023-04-06 0:21 ` [PATCH v8 6/7] net/mlx5: " Maciej W. Rozycki
2023-04-06 0:21 ` Maciej W. Rozycki
2023-04-06 0:21 ` [PATCH v8 7/7] PCI: Work around PCIe link training failures Maciej W. Rozycki
2023-04-06 0:21 ` Maciej W. Rozycki
2023-05-04 22:20 ` Bjorn Helgaas
2023-05-04 22:20 ` Bjorn Helgaas
2023-05-07 18:33 ` Maciej W. Rozycki
2023-05-07 18:33 ` Maciej W. Rozycki
2023-05-14 20:54 ` Maciej W. Rozycki [this message]
2023-05-14 20:54 ` Maciej W. Rozycki
2023-06-11 17:14 ` Maciej W. Rozycki
2023-06-11 17:14 ` Maciej W. Rozycki
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=alpine.DEB.2.21.2305142145320.11892@angie.orcam.me.uk \
--to=macro@orcam.me.uk \
--cc=alex.williamson@redhat.com \
--cc=bhelgaas@google.com \
--cc=christophe.leroy@csgroup.eu \
--cc=davem@davemloft.net \
--cc=david.abdurachmanov@gmail.com \
--cc=edumazet@google.com \
--cc=helgaas@kernel.org \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lukas@wunner.de \
--cc=mahesh@linux.ibm.com \
--cc=mika.westerberg@linux.intel.com \
--cc=mpe@ellerman.id.au \
--cc=netdev@vger.kernel.org \
--cc=npiggin@gmail.com \
--cc=oohall@gmail.com \
--cc=pabeni@redhat.com \
--cc=pali@kernel.org \
--cc=saeedm@nvidia.com \
--cc=sr@denx.de \
--cc=wilson@tuliptree.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.