From: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>
To: Kees Cook <keescook@chromium.org>
Cc: kernel@collabora.com,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"Nícolas F. R. A. Prado" <nfraprado@collabora.com>,
"Guilherme G. Piccoli" <gpiccoli@igalia.com>,
"Tony Luck" <tony.luck@intel.com>,
linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 1/2] pstore/ram: Register to module device table
Date: Wed, 10 Jan 2024 18:05:02 -0300 [thread overview]
Message-ID: <20240110210600.787703-2-nfraprado@collabora.com> (raw)
In-Reply-To: <20240110210600.787703-1-nfraprado@collabora.com>
Register the compatible for this module on the module device table so
it can be automatically loaded when a matching DT node is present,
allowing logging of panics and oopses without any intervention.
Signed-off-by: Nícolas F. R. A. Prado <nfraprado@collabora.com>
---
fs/pstore/ram.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/fs/pstore/ram.c b/fs/pstore/ram.c
index 88b34fdbf759..b1a455f42e93 100644
--- a/fs/pstore/ram.c
+++ b/fs/pstore/ram.c
@@ -893,6 +893,7 @@ static const struct of_device_id dt_match[] = {
{ .compatible = "ramoops" },
{}
};
+MODULE_DEVICE_TABLE(of, dt_match);
static struct platform_driver ramoops_driver = {
.probe = ramoops_probe,
--
2.43.0
next prev parent reply other threads:[~2024-01-10 21:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 21:05 [PATCH 0/2] Enable PSTORE_RAM as a module in the arm64 defconfig Nícolas F. R. A. Prado
2024-01-10 21:05 ` Nícolas F. R. A. Prado [this message]
2024-01-11 12:11 ` [PATCH 1/2] pstore/ram: Register to module device table AngeloGioacchino Del Regno
2024-01-11 18:22 ` Kees Cook
2024-01-10 21:05 ` [PATCH 2/2] arm64: defconfig: Enable PSTORE_RAM Nícolas F. R. A. Prado
2024-01-11 18:23 ` Kees Cook
2024-01-11 20:08 ` David
2024-02-01 17:58 ` [PATCH 0/2] Enable PSTORE_RAM as a module in the arm64 defconfig Kees Cook
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=20240110210600.787703-2-nfraprado@collabora.com \
--to=nfraprado@collabora.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=gpiccoli@igalia.com \
--cc=keescook@chromium.org \
--cc=kernel@collabora.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).