Devicetree
 help / color / mirror / Atom feed
From: Shubhrajyoti Datta <shubhrajyoti.datta@amd.com>
To: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-edac@vger.kernel.org>
Cc: <git@amd.com>, <ptsm@linux.microsoft.com>,
	<srivatsa@csail.mit.edu>, <shubhrajyoti.datta@gmail.com>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	"Borislav Petkov" <bp@alien8.de>, Tony Luck <tony.luck@intel.com>,
	James Morse <james.morse@arm.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	"Robert Richter" <rric@kernel.org>,
	Shubhrajyoti Datta <shubhrajyoti.datta@amd.com>
Subject: [PATCH v6 4/6] ras: Export log_non_standard_event for External Usage
Date: Thu, 24 Apr 2025 18:51:16 +0530	[thread overview]
Message-ID: <20250424132118.17074-5-shubhrajyoti.datta@amd.com> (raw)
In-Reply-To: <20250424132118.17074-1-shubhrajyoti.datta@amd.com>

The function log_non_standard_event is responsible for logging
platform-specific or vendor-defined RAS (Reliability, Availability,
and Serviceability) events. Currently, this function is only available
within the RAS subsystem, preventing external modules from
leveraging its capabilities.

log_non_standard_event is exported so that external drivers like VersalNet
EDAC can log non-standard RAS events.

Signed-off-by: Shubhrajyoti Datta <shubhrajyoti.datta@amd.com>
---

Changes in v6:
- Update the commit message.

Changes in v2:
- New patch addition

 drivers/ras/ras.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/ras/ras.c b/drivers/ras/ras.c
index a6e4792a1b2e..ac0e132ccc3e 100644
--- a/drivers/ras/ras.c
+++ b/drivers/ras/ras.c
@@ -51,6 +51,7 @@ void log_non_standard_event(const guid_t *sec_type, const guid_t *fru_id,
 {
 	trace_non_standard_event(sec_type, fru_id, fru_text, sev, err, len);
 }
+EXPORT_SYMBOL_GPL(log_non_standard_event);
 
 void log_arm_hw_error(struct cper_sec_proc_arm *err)
 {
-- 
2.17.1


  parent reply	other threads:[~2025-04-24 13:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-24 13:21 [PATCH v6 0/6] EDAC/Versal NET: Add support for error notification Shubhrajyoti Datta
2025-04-24 13:21 ` [PATCH v6 1/6] cdx: add the cdx headers to include/linux Shubhrajyoti Datta
2025-04-25  6:56   ` Krzysztof Kozlowski
2025-04-24 13:21 ` [PATCH v6 2/6] cdx: Add DDRMC Commands for DDR Configuration Retrieval Shubhrajyoti Datta
2025-04-24 13:21 ` [PATCH v6 3/6] cdx: Export Symbols for MCDI RPC and Initialization Shubhrajyoti Datta
2025-04-25  6:57   ` Krzysztof Kozlowski
2025-04-24 13:21 ` Shubhrajyoti Datta [this message]
2025-04-24 13:21 ` [PATCH v6 5/6] dt-bindings: memory-controllers: Add support for Versal NET EDAC Shubhrajyoti Datta
2025-04-25  7:03   ` Krzysztof Kozlowski
2025-04-24 13:21 ` [PATCH v6 6/6] EDAC/VersalNET: Add support for error notification Shubhrajyoti Datta

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=20250424132118.17074-5-shubhrajyoti.datta@amd.com \
    --to=shubhrajyoti.datta@amd.com \
    --cc=bp@alien8.de \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=git@amd.com \
    --cc=james.morse@arm.com \
    --cc=krzk@kernel.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=ptsm@linux.microsoft.com \
    --cc=robh@kernel.org \
    --cc=rric@kernel.org \
    --cc=shubhrajyoti.datta@gmail.com \
    --cc=srivatsa@csail.mit.edu \
    --cc=tony.luck@intel.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