From: Sebastian Reichel <sebastian.reichel@collabora.com> To: Arnd Bergmann <arnd@arndb.de>, Catalin Marinas <catalin.marinas@arm.com>, Will Deacon <will@kernel.org>, Russell King <linux@armlinux.org.uk>, Heiko Stuebner <heiko@sntech.de>, Lee Jones <lee@kernel.org> Cc: Marek Szyprowski <m.szyprowski@samsung.com>, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Sebastian Reichel <sebastian.reichel@collabora.com>, kernel@collabora.com Subject: [PATCH v8 0/2] MFD_RK8XX defconfig update Date: Thu, 18 May 2023 06:05:39 +0200 [thread overview] Message-ID: <20230518040541.299189-1-sebastian.reichel@collabora.com> (raw) Hi, I missed updating the defconfigs in the RK806 patchset [0]. Here are incremental patches doing just that. Considering the current status it's probably best for them to be added to the immutable branch prepared by Lee. [0] https://lore.kernel.org/all/20230504173618.142075-1-sebastian.reichel@collabora.com/ Thanks, -- Sebastian Sebastian Reichel (2): arm64: defconfig: update RK8XX MFD config ARM: multi_v7_defconfig: update MFD_RK808 name arch/arm/configs/multi_v7_defconfig | 2 +- arch/arm64/configs/defconfig | 3 ++- 2 files changed, 3 insertions(+), 2 deletions(-) -- 2.39.2
WARNING: multiple messages have this Message-ID (diff)
From: Sebastian Reichel <sebastian.reichel@collabora.com> To: Arnd Bergmann <arnd@arndb.de>, Catalin Marinas <catalin.marinas@arm.com>, Will Deacon <will@kernel.org>, Russell King <linux@armlinux.org.uk>, Heiko Stuebner <heiko@sntech.de>, Lee Jones <lee@kernel.org> Cc: Marek Szyprowski <m.szyprowski@samsung.com>, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Sebastian Reichel <sebastian.reichel@collabora.com>, kernel@collabora.com Subject: [PATCH v8 0/2] MFD_RK8XX defconfig update Date: Thu, 18 May 2023 06:05:39 +0200 [thread overview] Message-ID: <20230518040541.299189-1-sebastian.reichel@collabora.com> (raw) Hi, I missed updating the defconfigs in the RK806 patchset [0]. Here are incremental patches doing just that. Considering the current status it's probably best for them to be added to the immutable branch prepared by Lee. [0] https://lore.kernel.org/all/20230504173618.142075-1-sebastian.reichel@collabora.com/ Thanks, -- Sebastian Sebastian Reichel (2): arm64: defconfig: update RK8XX MFD config ARM: multi_v7_defconfig: update MFD_RK808 name arch/arm/configs/multi_v7_defconfig | 2 +- arch/arm64/configs/defconfig | 3 ++- 2 files changed, 3 insertions(+), 2 deletions(-) -- 2.39.2 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2023-05-18 4:06 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-18 4:05 Sebastian Reichel [this message] 2023-05-18 4:05 ` [PATCH v8 0/2] MFD_RK8XX defconfig update Sebastian Reichel 2023-05-18 4:05 ` [PATCH v8 1/2] arm64: defconfig: update RK8XX MFD config Sebastian Reichel 2023-05-18 4:05 ` Sebastian Reichel 2023-05-18 4:05 ` [PATCH v8 2/2] ARM: multi_v7_defconfig: update MFD_RK808 name Sebastian Reichel 2023-05-18 4:05 ` Sebastian Reichel
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=20230518040541.299189-1-sebastian.reichel@collabora.com \ --to=sebastian.reichel@collabora.com \ --cc=arnd@arndb.de \ --cc=catalin.marinas@arm.com \ --cc=heiko@sntech.de \ --cc=kernel@collabora.com \ --cc=lee@kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux@armlinux.org.uk \ --cc=m.szyprowski@samsung.com \ --cc=will@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: linkBe 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.