mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hans Zhang <18255117159@163.com>
To: Manivannan Sadhasivam <mani@kernel.org>
Cc: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
	lpieralisi@kernel.org, kw@linux.com, robh@kernel.org,
	bhelgaas@google.com, bwawrzyn@cisco.com, cassel@kernel.org,
	wojciech.jasko-EXT@continental-corporation.com, a-verma1@ti.com,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	rockswang7@gmail.com
Subject: Re: [v3] PCI: cadence: Fix sending message with data or without data
Date: Sat, 15 Feb 2025 00:53:36 +0800	[thread overview]
Message-ID: <f7e51e84-721c-4177-9a00-94ca466c145b@163.com> (raw)
In-Reply-To: <20250214155725.jpkd4vtcycav4yrc@thinkpad>



On 2025/2/14 23:57, Manivannan Sadhasivam wrote:
> On Fri, Feb 14, 2025 at 11:48:16PM +0800, Hans Zhang wrote:
>>> If so, it is fine. But is there a way we could detect those first generation IPs
>>> and flag it to users about broken MSG TLP support? Atleast, that would make the
>>> users aware of broken hw.
>>
>> I don't know how to do it, but here are the questions that were actually
>> tested.
>>
> 
> Not related to this patch, but please check if it is possible to detect those
> controllers.

If possible, I'll try to find an opportunity to check it out.

Best regards
Hans


  reply	other threads:[~2025-02-14 16:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-07 10:39 Hans Zhang
2025-02-14  7:30 ` Manivannan Sadhasivam
2025-02-14  8:23   ` Hans Zhang
2025-02-14 13:21     ` Manivannan Sadhasivam
2025-02-14 14:28       ` Hans Zhang
2025-02-14 15:31         ` Manivannan Sadhasivam
2025-02-14 15:48           ` Hans Zhang
2025-02-14 15:57             ` Manivannan Sadhasivam
2025-02-14 16:53               ` Hans Zhang [this message]
2025-02-14 16:06 ` Manivannan Sadhasivam
2025-02-14 16:49   ` Hans Zhang

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=f7e51e84-721c-4177-9a00-94ca466c145b@163.com \
    --to=18255117159@163.com \
    --cc=a-verma1@ti.com \
    --cc=bhelgaas@google.com \
    --cc=bwawrzyn@cisco.com \
    --cc=cassel@kernel.org \
    --cc=kw@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=mani@kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=robh@kernel.org \
    --cc=rockswang7@gmail.com \
    --cc=wojciech.jasko-EXT@continental-corporation.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

all inboxes | Powered by JetHome®