From: Krzysztof Kozlowski <krzk@kernel.org>
To: WangYuli <wangyuli@uniontech.com>,
tsbogend@alpha.franken.de, dhowells@redhat.com,
jlayton@kernel.org
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
chenhuacai@kernel.org, kernel@xen0n.name,
jiaxun.yang@flygoat.com, guanwentao@uniontech.com,
zhanjun@uniontech.com, xuerpeng@uniontech.com,
maqianga@uniontech.com, baimingcong@uniontech.com
Subject: Re: [PATCH 2/2] MIPS: loongson3_defconfig: Enable blk_dev_nvme by default
Date: Sun, 3 Nov 2024 17:44:09 +0100 [thread overview]
Message-ID: <ae2479fa-6a39-46b2-8712-2e33f2e0d53a@kernel.org> (raw)
In-Reply-To: <F56016A1645609BF+5d1de4afc8ee6bacf8878461b848de72b556c85f.1730638429.git.wangyuli@uniontech.com>
On 03/11/2024 14:00, WangYuli wrote:
> A significant number of 3A4000 machines come with NVMe drives
> pre-installed, so we should support it in its defconfig.
>
> Tested-by: Erpeng Xu <xuerpeng@uniontech.com>
> Tested-by: Qiang Ma <maqianga@uniontech.com>
I am sorry, but what exactly did you test here? This is defconfig, so
you checked whether after building kernel there is such module? This is
not testing.
...
> +CONFIG_BLK_DEV_NVME=m
Best regards,
Krzysztof
prev parent reply other threads:[~2024-11-03 16:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1730638429.git.wangyuli@uniontech.com>
2024-11-03 13:00 ` [PATCH 1/2] MIPS: loongson3_defconfig: Update configs dependencies WangYuli
2024-11-03 13:00 ` [PATCH 2/2] MIPS: loongson3_defconfig: Enable blk_dev_nvme by default WangYuli
2024-11-03 16:44 ` Krzysztof Kozlowski [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=ae2479fa-6a39-46b2-8712-2e33f2e0d53a@kernel.org \
--to=krzk@kernel.org \
--cc=baimingcong@uniontech.com \
--cc=chenhuacai@kernel.org \
--cc=dhowells@redhat.com \
--cc=guanwentao@uniontech.com \
--cc=jiaxun.yang@flygoat.com \
--cc=jlayton@kernel.org \
--cc=kernel@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=maqianga@uniontech.com \
--cc=tsbogend@alpha.franken.de \
--cc=wangyuli@uniontech.com \
--cc=xuerpeng@uniontech.com \
--cc=zhanjun@uniontech.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
Powered by JetHome