From: sashiko-bot@kernel.org
To: "Raag Jadav" <raag.jadav@intel.com>
Cc: linux-cxl@vger.kernel.org, intel-xe@lists.freedesktop.org,
linux-pci@vger.kernel.org
Subject: Re: [PATCH v2 1/2] PCI/AER: Export pcie_aer_is_native() to AER namespace
Date: Tue, 25 Aug 2026 05:49:39 +0000 [thread overview]
Message-ID: <20260825054940.55BA81F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260825054312.1319951-2-raag.jadav@intel.com>
> pcie_aer_is_native() was originally exported to CXL namespace in commit
> 49f776724e64 ("PCI/AER: Export pcie_aer_is_native()"). This is a bit
> misleading as the symbol or its underlying implementation does not reflect
> any distinguishable CXL functionality.
>
> Change this and export pcie_aer_is_native() to AER namespace, which is
> cleaner and more suitable for its implementation.
>
> Suggested-by: Lukas Wunner <lukas@wunner.de>
> Signed-off-by: Raag Jadav <raag.jadav@intel.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260825054312.1319951-1-raag.jadav@intel.com?part=1
next prev parent reply other threads:[~2026-08-25 5:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 5:42 [PATCH v2 0/2] Export pcie_aer_is_native() to AER namespace Raag Jadav
2026-08-25 5:42 ` [PATCH v2 1/2] PCI/AER: " Raag Jadav
2026-08-25 5:49 ` sashiko-bot [this message]
2026-08-25 14:18 ` Rodrigo Vivi
2026-08-25 15:05 ` Dave Jiang
2026-08-25 15:25 ` Rodrigo Vivi
2026-08-25 15:41 ` Dave Jiang
2026-08-25 15:00 ` Dave Jiang
2026-08-25 5:42 ` [PATCH v2 2/2] drm/xe/ras: Enable SGUnit PCIe error reporting Raag Jadav
2026-08-25 5:58 ` sashiko-bot
2026-08-26 21:26 ` Bjorn Helgaas
2026-08-25 7:21 ` ✓ CI.KUnit: success for Export pcie_aer_is_native() to AER namespace Patchwork
2026-08-25 8:00 ` ✓ Xe.CI.BAT: " Patchwork
2026-08-25 11:42 ` ✗ Xe.CI.FULL: failure " Patchwork
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=20260825054940.55BA81F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=raag.jadav@intel.com \
--cc=sashiko-reviews@lists.linux.dev \
/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.