From: "Arnd Bergmann" <arnd@arndb.de>
To: "Shawn Guo" <shawnguo2@yeah.net>, soc@kernel.org, arm <arm@kernel.org>
Cc: "Shawn Guo" <shawnguo@kernel.org>,
"Fabio Estevam" <festevam@gmail.com>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL 5/5] i.MX defconfig change for 6.11
Date: Mon, 08 Jul 2024 18:13:27 +0200 [thread overview]
Message-ID: <37bdee4b-cde6-496d-8217-80575c3e55ce@app.fastmail.com> (raw)
In-Reply-To: <20240702142153.413061-5-shawnguo2@yeah.net>
On Tue, Jul 2, 2024, at 16:21, Shawn Guo wrote:
> ----------------------------------------------------------------
> i.MX defconfig change for 6.11:
>
> - Enable a few drivers needed by TQMa7x/MBa7x and i.MX53 QSB/QSRB in
> imx_v6_v7_defconfig
> - Enable RAM block device and IWLWIFI driver support in arm64 defconfig
>
> Fabio Estevam (2):
> arm64: defconfig: Enable RAM block device support
I don't really like this one change. This has pretty much been
deprecated for decades, and I don't see a reason to enable
it now without a really good explanation.
Is there ever a reason for not using regular initramfs any more?
Shawn, can you resend the pull request without this one for
the moment?
Arnd
prev parent reply other threads:[~2024-07-08 16:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 14:21 [GIT PULL 1/5] i.MX SoC change for 6.11 Shawn Guo
2024-07-02 14:21 ` [GIT PULL 2/5] i.MX DT bindings " Shawn Guo
2024-07-02 14:21 ` [GIT PULL 3/5] i.MX ARM device tree change " Shawn Guo
2024-07-02 14:21 ` [GIT PULL 4/5] i.MX arm64 " Shawn Guo
2024-07-02 14:21 ` [GIT PULL 5/5] i.MX defconfig " Shawn Guo
2024-07-08 16:13 ` Arnd Bergmann [this message]
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=37bdee4b-cde6-496d-8217-80575c3e55ce@app.fastmail.com \
--to=arnd@arndb.de \
--cc=arm@kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=shawnguo2@yeah.net \
--cc=shawnguo@kernel.org \
--cc=soc@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