Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Niklas Cassel <cassel@kernel.org>
To: Hans Zhang <18255117159@163.com>
Cc: lpieralisi@kernel.org, kw@linux.com, bhelgaas@google.com,
	jingoohan1@gmail.com, manivannan.sadhasivam@linaro.org,
	robh@kernel.org, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH v2 2/3] PCI: mobiveil: Refactor link status check
Date: Tue, 13 May 2025 10:00:53 +0200	[thread overview]
Message-ID: <aCL8NXYC5mbGDRIX@ryzen> (raw)
In-Reply-To: <20250510160710.392122-3-18255117159@163.com>

On Sun, May 11, 2025 at 12:07:09AM +0800, Hans Zhang wrote:
> Update ls_g4_pcie_link_up() to return bool and simplify the LTSSM state
> check. Align function signature in pcie-mobiveil.h to match the change,
> ensuring consistency across the Mobiveil PCIe driver.
> 
> Signed-off-by: Hans Zhang <18255117159@163.com>
> Reviewed-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> ---

Reviewed-by: Niklas Cassel <cassel@kernel.org>

  reply	other threads:[~2025-05-13  8:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-10 16:07 [RESEND PATCH v2 0/3] Standardize link status check to return bool Hans Zhang
2025-05-10 16:07 ` [RESEND PATCH v2 1/3] PCI: dwc: " Hans Zhang
2025-05-13  8:00   ` Niklas Cassel
2025-05-10 16:07 ` [RESEND PATCH v2 2/3] PCI: mobiveil: Refactor link status check Hans Zhang
2025-05-13  8:00   ` Niklas Cassel [this message]
2025-05-10 16:07 ` [RESEND PATCH v2 3/3] PCI: cadence: Simplify j721e " Hans Zhang
2025-05-13  8:01   ` Niklas Cassel
2025-05-13  9:33 ` [RESEND PATCH v2 0/3] Standardize link status check to return bool Manivannan Sadhasivam
2025-05-16  8:52   ` Niklas Cassel
2025-05-16 14:57     ` Manivannan Sadhasivam
2025-05-13  9:40 ` Manivannan Sadhasivam
2025-05-13 14:42   ` Hans Zhang
2025-05-13 10:21 ` Krzysztof Wilczyński
2025-05-13 13:39   ` Niklas Cassel
2025-05-13 14:57     ` Krzysztof Wilczyński
2025-05-13 14:47   ` Hans Zhang
2025-05-13 15:04     ` Krzysztof Wilczyński
2025-05-13 15:09       ` Hans Zhang
2025-05-13 15:41         ` Niklas Cassel

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=aCL8NXYC5mbGDRIX@ryzen \
    --to=cassel@kernel.org \
    --cc=18255117159@163.com \
    --cc=bhelgaas@google.com \
    --cc=jingoohan1@gmail.com \
    --cc=kw@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=robh@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