mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hans Zhang <18255117159@163.com>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
	jingoohan1@gmail.com, lpieralisi@kernel.org, kw@linux.com
Cc: robh@kernel.org, bhelgaas@google.com, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org, shradha.t@samsung.com,
	cassel@kernel.org
Subject: Re: [PATCH 0/2] PCI: dwc-debugfs: Couple of fixes
Date: Wed, 26 Feb 2025 09:55:52 +0800	[thread overview]
Message-ID: <e25e5d68-7fb7-4157-825c-eb973f7e1321@163.com> (raw)
In-Reply-To: <20250225171239.19574-1-manivannan.sadhasivam@linaro.org>

Hi Mani,

Can you submit after this patch? Otherwise, will my patch conflict?

https://patchwork.kernel.org/project/linux-pci/patch/20250223141848.231232-1-18255117159@163.com/

Best regards
Hans

On 2025/2/26 01:12, Manivannan Sadhasivam wrote:
> Hi,
> 
> This series has a couple of fixes for the recently merged debugfs patches.
> This series is rebased on top of pci/controller/dwc branch.
> 
> - Mani
> 
> Manivannan Sadhasivam (2):
>    PCI: dwc-debugfs: Perform deinit only when the debugfs is initialized
>    PCI: dwc-debugfs: Return -EOPNOTSUPP if an event counter is not
>      supported
> 
>   .../controller/dwc/pcie-designware-debugfs.c   | 18 ++++++++++++++++++
>   1 file changed, 18 insertions(+)


  parent reply	other threads:[~2025-02-26  1:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-25 17:12 Manivannan Sadhasivam
2025-02-25 17:12 ` [PATCH 1/2] PCI: dwc-debugfs: Perform deinit only when the debugfs is initialized Manivannan Sadhasivam
2025-02-26  6:53   ` Krzysztof Wilczyński
2025-02-25 17:12 ` [PATCH 2/2] PCI: dwc-debugfs: Return -EOPNOTSUPP if an event counter is not supported Manivannan Sadhasivam
2025-02-26  6:56   ` Krzysztof Wilczyński
2025-02-26  1:55 ` Hans Zhang [this message]
2025-02-26  7:43   ` [PATCH 0/2] PCI: dwc-debugfs: Couple of fixes Krzysztof Wilczyński
2025-02-26  7:45     ` Hans Zhang
2025-02-26  7:17 ` Krzysztof Wilczyński

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=e25e5d68-7fb7-4157-825c-eb973f7e1321@163.com \
    --to=18255117159@163.com \
    --cc=bhelgaas@google.com \
    --cc=cassel@kernel.org \
    --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 \
    --cc=shradha.t@samsung.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®