All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Nam Cao <namcao@linutronix.de>
Cc: stable@vger.kernel.org,  jiajie.ho@starfivetech.com,
	palmer@rivosinc.com,  conor.dooley@microchip.com,
	linux-riscv@lists.infradead.org,  linux-kernel@vger.kernel.org
Subject: Re: Backport riscv kconfig for v6.6
Date: Mon, 11 Dec 2023 15:10:02 +0100	[thread overview]
Message-ID: <mvmwmtkq18l.fsf@suse.de> (raw)
In-Reply-To: <20231211145750.7bc2d378@namcao> (Nam Cao's message of "Mon, 11 Dec 2023 14:57:50 +0100")

On Dez 11 2023, Nam Cao wrote:

> Without this, it is not possible to configure the kernel with SPI drivers
> for the Visionfive 2 board.

Is it?  There is nothing that stops you from just enabling it.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: Andreas Schwab <schwab@suse.de>
To: Nam Cao <namcao@linutronix.de>
Cc: stable@vger.kernel.org,  jiajie.ho@starfivetech.com,
	palmer@rivosinc.com,  conor.dooley@microchip.com,
	linux-riscv@lists.infradead.org,  linux-kernel@vger.kernel.org
Subject: Re: Backport riscv kconfig for v6.6
Date: Mon, 11 Dec 2023 15:10:02 +0100	[thread overview]
Message-ID: <mvmwmtkq18l.fsf@suse.de> (raw)
In-Reply-To: <20231211145750.7bc2d378@namcao> (Nam Cao's message of "Mon, 11 Dec 2023 14:57:50 +0100")

On Dez 11 2023, Nam Cao wrote:

> Without this, it is not possible to configure the kernel with SPI drivers
> for the Visionfive 2 board.

Is it?  There is nothing that stops you from just enabling it.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

  reply	other threads:[~2023-12-11 14:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-11 13:57 Backport riscv kconfig for v6.6 Nam Cao
2023-12-11 13:57 ` Nam Cao
2023-12-11 14:10 ` Andreas Schwab [this message]
2023-12-11 14:10   ` Andreas Schwab
2023-12-11 14:11   ` Nam Cao
2023-12-11 14:11     ` Nam Cao
2023-12-11 14:15 ` [PATCH v6.1] riscv: Kconfig: Add select ARM_AMBA to SOC_STARFIVE Nam Cao
2023-12-11 14:15   ` Nam Cao

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=mvmwmtkq18l.fsf@suse.de \
    --to=schwab@suse.de \
    --cc=conor.dooley@microchip.com \
    --cc=jiajie.ho@starfivetech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=namcao@linutronix.de \
    --cc=palmer@rivosinc.com \
    --cc=stable@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.