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>,
"Arnd Bergmann" <arnd@arndb.de>,
"Bjorn Andersson" <quic_bjorande@quicinc.com>,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Dmitry Baryshkov" <dmitry.baryshkov@linaro.org>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"Guilherme G. Piccoli" <gpiccoli@igalia.com>,
"Konrad Dybcio" <konrad.dybcio@linaro.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
"Marek Szyprowski" <m.szyprowski@samsung.com>,
"Neil Armstrong" <neil.armstrong@linaro.org>,
"Tony Luck" <tony.luck@intel.com>,
"Will Deacon" <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] Enable PSTORE_RAM as a module in the arm64 defconfig
Date: Wed, 10 Jan 2024 18:05:01 -0300 [thread overview]
Message-ID: <20240110210600.787703-1-nfraprado@collabora.com> (raw)
This series enables the PSTORE_RAM config, aka the ramoops driver, in
the defconfig.
Nícolas F. R. A. Prado (2):
pstore/ram: Register to module device table
arm64: defconfig: Enable PSTORE_RAM
arch/arm64/configs/defconfig | 1 +
fs/pstore/ram.c | 1 +
2 files changed, 2 insertions(+)
--
2.43.0
next 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 Nícolas F. R. A. Prado [this message]
2024-01-10 21:05 ` [PATCH 1/2] pstore/ram: Register to module device table Nícolas F. R. A. Prado
2024-01-11 12:11 ` 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-1-nfraprado@collabora.com \
--to=nfraprado@collabora.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=geert+renesas@glider.be \
--cc=gpiccoli@igalia.com \
--cc=keescook@chromium.org \
--cc=kernel@collabora.com \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=neil.armstrong@linaro.org \
--cc=quic_bjorande@quicinc.com \
--cc=tony.luck@intel.com \
--cc=will@kernel.org \
/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).