mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: WangYuli <wangyuli@uniontech.com>
Cc: dhowells@redhat.com, jlayton@kernel.org,
	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 0/2] MIPS: loongson3_defconfig: Enable blk_dev_nvme by default
Date: Tue, 12 Nov 2024 15:58:23 +0100	[thread overview]
Message-ID: <ZzNtD+b4zgfdFUe7@alpha.franken.de> (raw)
In-Reply-To: <324362BC443F16F8+cover.1730638429.git.wangyuli@uniontech.com>

On Sun, Nov 03, 2024 at 09:00:03PM +0800, WangYuli wrote:
> A significant number of 3A4000 machines come with NVMe drives
> pre-installed, so we should support it in its defconfig.
> 
> To avoid confusion, update defconfig beforehand.
> 
> WangYuli (2):
>   MIPS: loongson3_defconfig: Update configs dependencies
>   MIPS: loongson3_defconfig: Enable blk_dev_nvme by default
> 
>  arch/mips/configs/loongson3_defconfig | 32 ++++++++-------------------
>  1 file changed, 9 insertions(+), 23 deletions(-)

series applied to mips-next.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

      reply	other threads:[~2024-11-12 15:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-03 13:00 WangYuli
2024-11-12 14:58 ` Thomas Bogendoerfer [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=ZzNtD+b4zgfdFUe7@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --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=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