From: Conor Dooley <conor@kernel.org> To: Emil Renner Berthing <kernel@esmil.dk>, Arnd Bergmann <arnd@arndb.de>, Palmer Dabbelt <palmer@dabbelt.com> Cc: Paul Walmsley <paul.walmsley@sifive.com>, Albert Ou <aou@eecs.berkeley.edu>, Nicolas Ferre <nicolas.ferre@microchip.com>, soc@kernel.org, linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org, Conor Dooley <conor.dooley@microchip.com> Subject: [PATCH v1 0/4] Route RISC-V SoC drivers/firmware/DT via the soc tree Date: Wed, 9 Nov 2022 21:22:16 +0000 [thread overview] Message-ID: <20221109212219.1598355-1-conor@kernel.org> (raw) From: Conor Dooley <conor.dooley@microchip.com> Spoke to Palmer today at the linux-riscv pw sync-up (see [0] for anyone that may see this and is interested), and he said go for it w/ MAINTAINERS changes. Routing patches this way was proposed by Palmer @ [1] where Arnd & I had a wee bit of back and forth about the maintainers entries required. I've CC'ed soc@kernel.org with the expectation that this series will go via the soc tree with Palmer's ack. I noticed while running the maintainers pattern check that I had messed up the i2c driver in an earlier submission - I think that Lukas may have flagged that but since It's not been fixed I've tacked on a patch for that too since I'm already in the area... Thanks, Conor. 0 - https://lore.kernel.org/linux-riscv/mhng-775d4068-6c1e-48a4-a1dc-b4a76ff26bb3@palmer-ri-x1c9a/ 1 - https://lore.kernel.org/linux-riscv/mhng-e4210f56-fcc3-4db8-abdb-d43b3ebe695d@palmer-ri-x1c9a/ Conor Dooley (4): MAINTAINERS: add entries for misc. RISC-V SoC drivers and devicetrees MAINTAINERS: generify the Microchip RISC-V entry name MAINTAINERS: add an entry for StarFive devicetrees MAINTAINERS: repair Microchip corei2c driver entry MAINTAINERS | 34 ++++++++++++++++++++++++++++++---- 1 file changed, 30 insertions(+), 4 deletions(-) -- 2.37.2
WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <conor@kernel.org> To: Emil Renner Berthing <kernel@esmil.dk>, Arnd Bergmann <arnd@arndb.de>, Palmer Dabbelt <palmer@dabbelt.com> Cc: Paul Walmsley <paul.walmsley@sifive.com>, Albert Ou <aou@eecs.berkeley.edu>, Nicolas Ferre <nicolas.ferre@microchip.com>, soc@kernel.org, linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org, Conor Dooley <conor.dooley@microchip.com> Subject: [PATCH v1 0/4] Route RISC-V SoC drivers/firmware/DT via the soc tree Date: Wed, 9 Nov 2022 21:22:16 +0000 [thread overview] Message-ID: <20221109212219.1598355-1-conor@kernel.org> (raw) From: Conor Dooley <conor.dooley@microchip.com> Spoke to Palmer today at the linux-riscv pw sync-up (see [0] for anyone that may see this and is interested), and he said go for it w/ MAINTAINERS changes. Routing patches this way was proposed by Palmer @ [1] where Arnd & I had a wee bit of back and forth about the maintainers entries required. I've CC'ed soc@kernel.org with the expectation that this series will go via the soc tree with Palmer's ack. I noticed while running the maintainers pattern check that I had messed up the i2c driver in an earlier submission - I think that Lukas may have flagged that but since It's not been fixed I've tacked on a patch for that too since I'm already in the area... Thanks, Conor. 0 - https://lore.kernel.org/linux-riscv/mhng-775d4068-6c1e-48a4-a1dc-b4a76ff26bb3@palmer-ri-x1c9a/ 1 - https://lore.kernel.org/linux-riscv/mhng-e4210f56-fcc3-4db8-abdb-d43b3ebe695d@palmer-ri-x1c9a/ Conor Dooley (4): MAINTAINERS: add entries for misc. RISC-V SoC drivers and devicetrees MAINTAINERS: generify the Microchip RISC-V entry name MAINTAINERS: add an entry for StarFive devicetrees MAINTAINERS: repair Microchip corei2c driver entry MAINTAINERS | 34 ++++++++++++++++++++++++++++++---- 1 file changed, 30 insertions(+), 4 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-09 21:23 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-09 21:22 Conor Dooley [this message] 2022-11-09 21:22 ` [PATCH v1 0/4] Route RISC-V SoC drivers/firmware/DT via the soc tree Conor Dooley 2022-11-09 21:22 ` [PATCH v1 1/4] MAINTAINERS: add entries for misc. RISC-V SoC drivers and devicetrees Conor Dooley 2022-11-09 21:22 ` Conor Dooley 2022-11-14 8:59 ` Nicolas Ferre 2022-11-14 8:59 ` Nicolas Ferre 2022-11-14 19:44 ` Palmer Dabbelt 2022-11-14 19:44 ` Palmer Dabbelt 2022-11-09 21:22 ` [PATCH v1 2/4] MAINTAINERS: generify the Microchip RISC-V entry name Conor Dooley 2022-11-09 21:22 ` Conor Dooley 2022-11-09 21:22 ` [PATCH v1 3/4] MAINTAINERS: add an entry for StarFive devicetrees Conor Dooley 2022-11-09 21:22 ` Conor Dooley 2022-11-10 8:48 ` Emil Renner Berthing 2022-11-10 8:48 ` Emil Renner Berthing 2022-11-09 21:22 ` [PATCH v1 4/4] MAINTAINERS: repair Microchip corei2c driver entry Conor Dooley 2022-11-09 21:22 ` Conor Dooley 2022-11-14 13:00 ` [PATCH v1 0/4] Route RISC-V SoC drivers/firmware/DT via the soc tree patchwork-bot+linux-soc
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=20221109212219.1598355-1-conor@kernel.org \ --to=conor@kernel.org \ --cc=aou@eecs.berkeley.edu \ --cc=arnd@arndb.de \ --cc=conor.dooley@microchip.com \ --cc=kernel@esmil.dk \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-riscv@lists.infradead.org \ --cc=nicolas.ferre@microchip.com \ --cc=palmer@dabbelt.com \ --cc=paul.walmsley@sifive.com \ --cc=soc@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.