All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: Shuai Xue <xueshuai@linux.alibaba.com>
Cc: bhelgaas@google.com, tony.luck@intel.com, bp@alien8.de,
	mhiramat@kernel.org, mathieu.desnoyers@efficios.com,
	oleg@redhat.com, naveen@kernel.org, davem@davemloft.net,
	anil.s.keshavamurthy@intel.com, mark.rutland@arm.com,
	peterz@infradead.org, rostedt@goodmis.org,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-edac@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH v4] PCI: hotplug: Add a generic RAS tracepoint for hotplug event
Date: Tue, 7 Jan 2025 13:53:26 +0100	[thread overview]
Message-ID: <Z30jxlgo63Js6G74@wunner.de> (raw)
In-Reply-To: <f77669b5-c174-48c7-8f0f-187d1f54ea91@linux.alibaba.com>

On Tue, Jan 07, 2025 at 07:30:28PM +0800, Shuai Xue wrote:
> 2024/11/23 19:31, Shuai Xue:
> > To this end, define a new TRACING_SYSTEM named pci, add a generic RAS
> > tracepoint for hotplug event to help healthy check, and generate
> > tracepoints for pcie hotplug event. To monitor these tracepoints in
> > userspace, e.g. with rasdaemon, put `enum pci_hotplug_event` in uapi
> > header.
[...]
> I would like to inquire that if there are any further actions required
> from my end to proceed for this patch?
> 
> Additionally, I would appreciate if you could inform me about who will be
> pick up this patch.

I'm fine with this patch, as indicated by the Reviewed-by,
so no actions required from you for now.  This will be
picked up by Bjorn once he gets to it (assuming he's happy with it).
A lot of folks were on holidays and are catching up on e-mails,
so please be patient.

Thanks,

Lukas

  reply	other threads:[~2025-01-07 12:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-23 11:31 [PATCH v4] PCI: hotplug: Add a generic RAS tracepoint for hotplug event Shuai Xue
2025-01-07 11:30 ` Shuai Xue
2025-01-07 12:53   ` Lukas Wunner [this message]
2025-01-08  1:47     ` Shuai Xue
2025-01-07 23:19 ` Bjorn Helgaas
2025-01-08  9:04   ` Shuai Xue
2025-01-08 17:59     ` Bjorn Helgaas
2025-01-09  1:40       ` Shuai Xue

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=Z30jxlgo63Js6G74@wunner.de \
    --to=lukas@wunner.de \
    --cc=anil.s.keshavamurthy@intel.com \
    --cc=bhelgaas@google.com \
    --cc=bp@alien8.de \
    --cc=davem@davemloft.net \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=naveen@kernel.org \
    --cc=oleg@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tony.luck@intel.com \
    --cc=xueshuai@linux.alibaba.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 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.