mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Priyank Rathod <rathodpriyank@google.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: "Bjorn Helgaas" <bhelgaas@google.com>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	"Lukas Wunner" <lukas@wunner.de>,
	"Manivannan Sadhasivam" <mani@kernel.org>,
	"Jonathan Corbet" <corbet@lwn.net>,
	"Shuah Khan" <skhan@linuxfoundation.org>,
	"Shuah Khan" <shuah@kernel.org>,
	"Randy Dunlap" <rdunlap@infradead.org>,
	linux-pci@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 0/2] PCI: Add Lane Margining at the Receiver debugfs interface
Date: Tue, 10 Nov 2026 00:24:37 +0000	[thread overview]
Message-ID: <20261110002437.2376944-1-rathodpriyank@google.com> (raw)
In-Reply-To: <20261012-pcie-link-endpoints-v7-0-36aba9c91f10@google.com>

Hi Bjorn, Ilpo, Lukas,

Gentle ping on this v7 series now that v7.4-rc1 is out (both patches
still apply cleanly to v7.4-rc1 and pci/next).

In v7:
  - Both pcie_get_link_endpoints() and pci_aspm_inhibit() are dropped per
    Ilpo's earlier feedback, leaving aspm.c, pci.c, and
    include/linux/pci.h untouched and using the existing ASPM API.
  - Retimer receiver discovery and margining coverage (receivers 2..5 via
    LNKSTA2) are included in the pcie_lmr kselftest.
  - Both patches passed Sashiko review with zero issues.

Please let me know if you have any feedback or would like any changes.

Thanks,
Priyank

      parent reply	other threads:[~2026-11-10  0:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-12 17:36 Priyank Rathod
2026-10-12 17:36 ` [PATCH v7 1/2] PCI/LMR: " Priyank Rathod
2026-10-12 17:36 ` [PATCH v7 2/2] selftests/pcie_lmr: Add tests for the Lane Margining " Priyank Rathod
2026-11-10  0:24 ` Priyank Rathod [this message]

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=20261110002437.2376944-1-rathodpriyank@google.com \
    --to=rathodpriyank@google.com \
    --cc=bhelgaas@google.com \
    --cc=corbet@lwn.net \
    --cc=helgaas@kernel.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=mani@kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=shuah@kernel.org \
    --cc=skhan@linuxfoundation.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
all inboxes | Powered by JetHome®