All of lore.kernel.org
 help / color / mirror / Atom feed
From: Niklas Cassel <cassel@kernel.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: lpieralisi@kernel.org, kw@linux.com, bhelgaas@google.com,
	jingoohan1@gmail.com, Hans Zhang <18255117159@163.com>,
	robh@kernel.org, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH v2 0/3] Standardize link status check to return bool
Date: Fri, 16 May 2025 10:52:17 +0200	[thread overview]
Message-ID: <aCb8wauW4h85F8YS@ryzen> (raw)
In-Reply-To: <174712882946.9059.1080501209546808704.b4-ty@linaro.org>

Hello Mani,

On Tue, May 13, 2025 at 10:33:59AM +0100, Manivannan Sadhasivam wrote:
> 
> On Sun, 11 May 2025 00:07:07 +0800, Hans Zhang wrote:
> > 1. PCI: dwc: Standardize link status check to return bool.
> > 2. PCI: mobiveil: Refactor link status check.
> > 3. PCI: cadence: Simplify j721e link status check.
> > 
> 
> Applied, thanks!
> 
> [1/3] PCI: dwc: Standardize link status check to return bool
>       commit: f46bfb1d3c6a601caad90eb3c11a1e1e17cccb1a
> [2/3] PCI: mobiveil: Refactor link status check
>       commit: 0a9d6a3d0fd1650b9ee00bc8150828e19cadaf23
> [3/3] PCI: cadence: Simplify j721e link status check
>       commit: 1a176b25f5d6f00c6c44729c006379b9a6dbc703
> 

This was all applied to the dw-rockchip branch.

Was that intentional?

My guess is that perhaps you thought that
"PCI: dwc: Standardize link status check to return bool"
was going to conflict with Hans's other commit:
5e5a3bf48eed ("PCI: dw-rockchip: Use rockchip_pcie_link_up() to check link
up instead of open coding")

but at least from looking at the diff, they don't seem to touch the same
lines, but perhaps you got a conflict anyway?



mobiveil and cadence patches seem unrelated to dw-rockchip
(unrelated to DWC even).

If it was intentional, all is good, but perhaps the branch
should have a more generic name, rather than dw-rockchip,
especially now when the reset-slot and qcom-reset slot patches
are also on the same branch.


Kind regards,
Niklas

  reply	other threads:[~2025-05-16  8:52 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
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 [this message]
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=aCb8wauW4h85F8YS@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 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.