From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
To: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
Cc: openbmc@lists.ozlabs.org, Joel Stanley <joel@jms.id.au>,
Russell King <linux@armlinux.org.uk>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4] ARM: Add wpcm450_defconfig for Nuvoton WPCM450
Date: Sun, 29 Jan 2023 05:30:10 +0100 [thread overview]
Message-ID: <Y9X2Ur6oHTsFtCmW@probook> (raw)
In-Reply-To: <20230129041547.942335-1-j.neuschaefer@gmx.net>
[-- Attachment #1: Type: text/plain, Size: 1251 bytes --]
On Sun, Jan 29, 2023 at 05:15:46AM +0100, Jonathan Neuschäfer wrote:
> This defconfig aims to offer a reasonable set of defaults for all
> systems running on a Nuvoton WPCM450 chip.
>
> Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
> Reviewed-by: Joel Stanley <joel@jms.id.au>
> ---
Sorry, I hadn't noticed that v3 already made it into linux-next.
@Joel: I'll leave it up to you to decide whether you keep v3 or replace
it with v4 (although given the upcoming merge window, I guess keeping v3
is safer).
Best regards,
Jonathan
> v4:
> - Add Joel's R-b
> - Disable CPU_FREQ
> - Update for Linux 6.2: Enable CONFIG_SPI_WPCM_FIU, disable
> CONFIG_LEGACY_TIOCSTI
> - Disable CONFIG_KEXEC, which isn't generally useful for the BMC usecase
>
> v3:
> - https://lore.kernel.org/lkml/20221101112134.673869-1-j.neuschaefer@gmx.net/
> - Regenerate for 6.1-rc1 and enable a few Nuvoton-specific options as
> well as the PECI subsystem
>
> v2:
> - Regenerate for 5.19-rc1
> ---
> MAINTAINERS | 1 +
> arch/arm/configs/wpcm450_defconfig | 211 +++++++++++++++++++++++++++++
> 2 files changed, 212 insertions(+)
> create mode 100644 arch/arm/configs/wpcm450_defconfig
[...]
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-01-29 4:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-29 4:15 [PATCH v4] ARM: Add wpcm450_defconfig for Nuvoton WPCM450 Jonathan Neuschäfer
2023-01-29 4:30 ` Jonathan Neuschäfer [this message]
2023-02-01 5:17 ` Joel Stanley
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=Y9X2Ur6oHTsFtCmW@probook \
--to=j.neuschaefer@gmx.net \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=openbmc@lists.ozlabs.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