From: Conor Dooley <conor@kernel.org>
To: linux-riscv@lists.infradead.org
Cc: Conor Dooley <conor.dooley@microchip.com>,
Arnd Bergmann <arnd@arndb.de>,
Christoph Hellwig <hch@infradead.org>,
Damien Le Moal <damien.lemoal@opensource.wdc.com>,
Emil Renner Berthing <emil.renner.berthing@canonical.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Heiko Stuebner <heiko@sntech.de>,
Palmer Dabbelt <palmer@dabbelt.com>,
Samuel Holland <samuel@sholland.org>
Subject: [PATCH v1 0/7] RISC-V: kconfig.socs cleanup, part 1
Date: Mon, 21 Nov 2022 22:14:08 +0000 [thread overview]
Message-ID: <20221121221414.109965-1-conor@kernel.org> (raw)
From: Conor Dooley <conor.dooley@microchip.com>
Hey all,
Following on from my RFC series a little bit ago, I'm back again with an
attempted conversion of our SOC_FOO symbols to a more uniform ARCH_FOO.
Last time around, I had about 30 patches [0], but here I have a more
modest offering.
Patch 1 adds stubs, that ideally would be applied for v6.2-rc1 (but
after week 1, see the note in that patch for more), which would allow
for converting drivers etc over a release cycle (or more) while allowing
everything else to keep working in the meantime.
Christoph Hellwig & Damien voiced some objections in the original thread,
hopefully the gradual conversion assuages Damien's concerns about
breaking defconfigs - but I am not sure what to do about Christoph's
dislike of the ARCH_FOO stuff. A change the world approach is unlikely
to be well received & introducing "duplicate" symbols for cross-arch
vendors would surely be similarly well received? I don't mind doing it,
but my instinct is that that is a futile use of time.
The rest of this series contains v6.3 material, converting SOC_FOO
usages in arch/riscv to ARCH_FOO.
Thanks,
Conor.
[0] - https://lore.kernel.org/linux-riscv/20220923185605.1900083-1-conor@kernel.org/
CC: Arnd Bergmann <arnd@arndb.de>
CC: Christoph Hellwig <hch@infradead.org>
CC: Conor.Dooley <conor.dooley@microchip.com>
CC: Damien Le Moal <damien.lemoal@opensource.wdc.com>
CC: Emil Renner Berthing <emil.renner.berthing@canonical.com>
CC: Geert Uytterhoeven <geert@linux-m68k.org>
CC: Heiko Stuebner <heiko@sntech.de>
CC: Palmer Dabbelt <palmer@dabbelt.com>
CC: Samuel Holland <samuel@sholland.org>
CC: linux-riscv@lists.infradead.org
Conor Dooley (7):
RISC-V: introduce ARCH_FOO kconfig aliases for SOC_FOO symbols
RISC-V: kconfig.socs: convert usage of SOC_CANAAN to ARCH_CANAAN
RISC-V: kbuild: convert all use of SOC_FOO to ARCH_FOO
RISC-V: stop selecting SIFIVE_PLIC at the SoC level
RISC-V: stop selecting the PolarFire SoC clock driver
RISC-V: stop selecting SiFive clock and serial drivers directly
RISC-V: stop directly selecting drivers for SOC_CANAAN
arch/riscv/Kconfig | 1 +
arch/riscv/Kconfig.socs | 44 +++++++++++++++-----------
arch/riscv/Makefile | 2 +-
arch/riscv/boot/dts/Makefile | 2 +-
arch/riscv/boot/dts/canaan/Makefile | 14 ++++----
arch/riscv/boot/dts/microchip/Makefile | 8 ++---
arch/riscv/boot/dts/sifive/Makefile | 4 +--
arch/riscv/boot/dts/starfive/Makefile | 2 +-
8 files changed, 43 insertions(+), 34 deletions(-)
--
2.37.2
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2022-11-21 22:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 22:14 Conor Dooley [this message]
2022-11-21 22:14 ` [PATCH v1 1/7] RISC-V: introduce ARCH_FOO kconfig aliases for SOC_FOO symbols Conor Dooley
2023-01-10 21:14 ` Geert Uytterhoeven
2023-01-10 21:39 ` Conor Dooley
2023-01-11 7:46 ` Geert Uytterhoeven
2023-01-10 22:22 ` Damien Le Moal
2023-01-10 22:34 ` Conor Dooley
2023-01-10 22:47 ` Damien Le Moal
2023-01-11 7:50 ` Geert Uytterhoeven
2022-11-21 22:14 ` [PATCH v1 2/7] RISC-V: kconfig.socs: convert usage of SOC_CANAAN to ARCH_CANAAN Conor Dooley
2022-11-21 22:14 ` [PATCH v1 3/7] RISC-V: kbuild: convert all use of SOC_FOO to ARCH_FOO Conor Dooley
2022-11-22 6:04 ` Christoph Hellwig
2022-12-09 1:24 ` Palmer Dabbelt
2022-11-21 22:14 ` [PATCH v1 4/7] RISC-V: stop selecting SIFIVE_PLIC at the SoC level Conor Dooley
2022-11-21 22:14 ` [PATCH v1 5/7] RISC-V: stop selecting the PolarFire SoC clock driver Conor Dooley
2022-11-22 8:35 ` Geert Uytterhoeven
2022-11-22 8:40 ` Conor.Dooley
2022-11-21 22:14 ` [PATCH v1 6/7] RISC-V: stop selecting SiFive clock and serial drivers directly Conor Dooley
2022-11-21 22:14 ` [PATCH v1 7/7] RISC-V: stop directly selecting drivers for SOC_CANAAN Conor Dooley
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=20221121221414.109965-1-conor@kernel.org \
--to=conor@kernel.org \
--cc=arnd@arndb.de \
--cc=conor.dooley@microchip.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=emil.renner.berthing@canonical.com \
--cc=geert@linux-m68k.org \
--cc=hch@infradead.org \
--cc=heiko@sntech.de \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=samuel@sholland.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;
as well as URLs for NNTP newsgroup(s).