From: Steven Rostedt <rostedt@goodmis.org>
To: Shuai Xue <xueshuai@linux.alibaba.com>
Cc: lukas@wunner.de, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-edac@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, helgaas@kernel.org,
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, tianruidong@linux.alibaba.com
Subject: Re: [PATCH v5] PCI: hotplug: Add a generic RAS tracepoint for hotplug event
Date: Mon, 10 Mar 2025 10:50:44 -0400 [thread overview]
Message-ID: <20250310105044.129dc354@gandalf.local.home> (raw)
In-Reply-To: <deb6f0c4-77b8-431e-9b81-555a8344c750@linux.alibaba.com>
On Mon, 10 Mar 2025 11:59:55 +0800
Shuai Xue <xueshuai@linux.alibaba.com> wrote:
> Hi, Steve,
>
> If I move PCI_HOTPLUG_EVENT into one place, `include/upai/linux/pci.h`,
> I need to include:
>
> #include <linux/tracepoint.h>
>
> Then, kernel build fails with CONFIG_UAPI_HEADER_TEST=y:
Just move the enum definitions, not the entire event file.
That is, have one place has the PCI_HOTPLUG_EVENT macro, and have both the
uapi header as well as the tracepoint header include that header.
I guess I need to see the entire change.
-- Steve
next prev parent reply other threads:[~2025-03-10 14:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 2:55 [PATCH v5] PCI: hotplug: Add a generic RAS tracepoint for hotplug event Shuai Xue
2025-01-13 20:55 ` Steven Rostedt
2025-01-14 11:47 ` Shuai Xue
2025-03-10 3:59 ` Shuai Xue
2025-03-10 14:50 ` Steven Rostedt [this message]
2025-03-11 2:06 ` 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=20250310105044.129dc354@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=anil.s.keshavamurthy@intel.com \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=davem@davemloft.net \
--cc=helgaas@kernel.org \
--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=lukas@wunner.de \
--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=tianruidong@linux.alibaba.com \
--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.