From: Conor Dooley <conor@kernel.org> To: William Qiu <william.qiu@starfivetech.com> Cc: devicetree@vger.kernel.org, linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Emil Renner Berthing <kernel@esmil.dk> Subject: Re: [RESEND v6 2/2] riscv: dts: starfive: Add syscon node Date: Wed, 15 Mar 2023 18:57:51 +0000 [thread overview] Message-ID: <a3338a34-11f7-4770-a475-95e1a83f9cc9@spud> (raw) In-Reply-To: <20230315055813.94740-3-william.qiu@starfivetech.com> [-- Attachment #1: Type: text/plain, Size: 55 bytes --] Reviewed-by: Conor Dooley <conor.dooley@microchip.com> [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 228 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <conor@kernel.org> To: William Qiu <william.qiu@starfivetech.com> Cc: devicetree@vger.kernel.org, linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Emil Renner Berthing <kernel@esmil.dk> Subject: Re: [RESEND v6 2/2] riscv: dts: starfive: Add syscon node Date: Wed, 15 Mar 2023 18:57:51 +0000 [thread overview] Message-ID: <a3338a34-11f7-4770-a475-95e1a83f9cc9@spud> (raw) In-Reply-To: <20230315055813.94740-3-william.qiu@starfivetech.com> [-- Attachment #1.1: Type: text/plain, Size: 55 bytes --] Reviewed-by: Conor Dooley <conor.dooley@microchip.com> [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 228 bytes --] [-- Attachment #2: Type: text/plain, Size: 161 bytes --] _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-03-15 18:58 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-15 5:58 [RESEND v6 0/2] StarFive's SDIO/eMMC driver support William Qiu 2023-03-15 5:58 ` William Qiu 2023-03-15 5:58 ` [RESEND v6 1/2] dt-bindings: soc: starfive: Add StarFive syscon doc William Qiu 2023-03-15 5:58 ` William Qiu 2023-03-15 19:00 ` Conor Dooley 2023-03-15 19:00 ` Conor Dooley 2023-03-19 12:27 ` Krzysztof Kozlowski 2023-03-19 12:27 ` Krzysztof Kozlowski 2023-03-20 5:54 ` William Qiu 2023-03-20 5:54 ` William Qiu 2023-03-20 6:38 ` Krzysztof Kozlowski 2023-03-20 6:38 ` Krzysztof Kozlowski 2023-03-20 7:32 ` William Qiu 2023-03-20 7:32 ` William Qiu 2023-04-05 16:38 ` Conor Dooley 2023-04-05 16:38 ` Conor Dooley 2023-04-06 2:20 ` William Qiu 2023-04-06 2:20 ` William Qiu 2023-03-19 12:29 ` Krzysztof Kozlowski 2023-03-19 12:29 ` Krzysztof Kozlowski 2023-03-20 6:00 ` William Qiu 2023-03-20 6:00 ` William Qiu 2023-03-20 6:38 ` Krzysztof Kozlowski 2023-03-20 6:38 ` Krzysztof Kozlowski 2023-03-20 7:31 ` William Qiu 2023-03-20 7:31 ` William Qiu 2023-03-15 5:58 ` [RESEND v6 2/2] riscv: dts: starfive: Add syscon node William Qiu 2023-03-15 5:58 ` William Qiu 2023-03-15 18:57 ` Conor Dooley [this message] 2023-03-15 18:57 ` Conor Dooley 2023-03-15 21:03 ` Emil Renner Berthing 2023-03-15 21:03 ` Emil Renner Berthing
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=a3338a34-11f7-4770-a475-95e1a83f9cc9@spud \ --to=conor@kernel.org \ --cc=devicetree@vger.kernel.org \ --cc=kernel@esmil.dk \ --cc=krzysztof.kozlowski+dt@linaro.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-riscv@lists.infradead.org \ --cc=robh+dt@kernel.org \ --cc=william.qiu@starfivetech.com \ /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.