[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250724225752.42af5c45@gandalf.local.home>
Date: Thu, 24 Jul 2025 22:57:52 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Shuai Xue <xueshuai@...ux.alibaba.com>
Cc: kernel test robot <lkp@...el.com>, Bjorn Helgaas <bhelgaas@...gle.com>,
lukas@...ner.de, linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-edac@...r.kernel.org, linux-trace-kernel@...r.kernel.org,
helgaas@...nel.org, ilpo.jarvinen@...ux.intel.com, mattc@...estorage.com,
Jonathan.Cameron@...wei.com, oe-kbuild-all@...ts.linux.dev,
tony.luck@...el.com, bp@...en8.de, mhiramat@...nel.org,
mathieu.desnoyers@...icios.com, oleg@...hat.com, naveen@...nel.org,
davem@...emloft.net, anil.s.keshavamurthy@...el.com, mark.rutland@....com,
peterz@...radead.org, tianruidong@...ux.alibaba.com
Subject: Re: [PATCH v9 2/2] PCI: trace: Add a RAS tracepoint to monitor link
speed changes
On Fri, 25 Jul 2025 10:31:45 +0800
Shuai Xue <xueshuai@...ux.alibaba.com> wrote:
> I'm leaning toward option 1 (dedicated trace.c file) as it's the
> cleanest approach and follows the pattern used in other subsystems. Does
> that sound reasonable to you?
That's fine, but make sure you have #ifdef CONFIG_FOO around tracepoints
that are only used when those configs are enabled, otherwise you will get
warnings.
Well, if they are exported, then the warnings are suppressed.
https://lore.kernel.org/all/20250725025149.726267838@kernel.org/
-- Steve
Powered by blists - more mailing lists