From: "Guido Günther" <agx@sigxcpu•org>
To: "Catalin Marinas" <catalin.marinas@arm•com>,
"Will Deacon" <will@kernel•org>,
"Bjorn Andersson" <bjorn.andersson@linaro•org>,
"Shawn Guo" <shawnguo@kernel•org>, "Li Yang" <leoyang.li@nxp•com>,
"Geert Uytterhoeven" <geert+renesas@glider•be>,
"Vinod Koul" <vkoul@kernel•org>,
"Guido Günther" <agx@sigxcpu•org>,
"Anson Huang" <Anson.Huang@nxp•com>,
"Michael Walle" <michael@walle•cc>,
"Max Krummenacher" <max.oss.09@gmail•com>,
linux-arm-kernel@lists•infradead.org,
linux-kernel@vger•kernel.org
Subject: [PATCH v1 0/3] arm64: defconfig: Enable some (hopefully) useful options
Date: Fri, 18 Dec 2020 18:32:05 +0100 [thread overview]
Message-ID: <cover.1608312654.git.agx@sigxcpu.org> (raw)
The aim of this series is make the arm64 'make defconfig' kernel more useful
for debugging and daily usage. I'm aware that expectations there diff widely so
I went for things I found in other defconigs as well.
It enables ftrace, more filesystems and more dm/md modules.
Since it's not board specific I have no idea which tree I would target so I
picked next-20201218.
Guido Günther (3):
arm64: defconfig: Enable function tracer
arm64: defconfig: Enable more filesystems
arm64: defconfig: Enable more DM/MD targets as modules
arch/arm64/configs/defconfig | 26 ++++++++++++++++++++++++--
1 file changed, 24 insertions(+), 2 deletions(-)
--
2.29.2
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-12-18 18:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-18 17:32 Guido Günther [this message]
2020-12-18 17:32 ` [PATCH v1 1/3] arm64: defconfig: Enable function tracer Guido Günther
2020-12-18 17:32 ` [PATCH v1 2/3] arm64: defconfig: Enable more filesystems Guido Günther
2020-12-18 17:32 ` [PATCH v1 3/3] arm64: defconfig: Enable more DM/MD targets as modules Guido Günther
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=cover.1608312654.git.agx@sigxcpu.org \
--to=agx@sigxcpu$(echo .)org \
--cc=Anson.Huang@nxp$(echo .)com \
--cc=bjorn.andersson@linaro$(echo .)org \
--cc=catalin.marinas@arm$(echo .)com \
--cc=geert+renesas@glider$(echo .)be \
--cc=leoyang.li@nxp$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=max.oss.09@gmail$(echo .)com \
--cc=michael@walle$(echo .)cc \
--cc=shawnguo@kernel$(echo .)org \
--cc=vkoul@kernel$(echo .)org \
--cc=will@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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