From: <Conor.Dooley@microchip.com>
To: <bmeng.cn@gmail.com>, <palmer@dabbelt.com>,
<paul.walmsley@sifive.com>, <atish.patra@wdc.com>,
<linux-kernel@vger.kernel.org>, <linux-riscv@lists.infradead.org>,
<Daire.McNamara@microchip.com>
Cc: <bin.meng@windriver.com>
Subject: Re: [PATCH 1/2] riscv: dts: microchip: Drop "clock-frequency" property of cpu nodes
Date: Fri, 9 Jul 2021 08:42:10 +0000 [thread overview]
Message-ID: <48f0a6c0-13af-e2bd-6849-e84448f71b51@microchip.com> (raw)
In-Reply-To: <CAEUhbmXQt0pnqvzCGwGU38_U0qRZRmgGA4qgaFT_HevbSZRDBg@mail.gmail.com>
On 08/07/2021 14:39, Bin Meng wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> On Wed, Jun 16, 2021 at 2:02 PM Bin Meng <bmeng.cn@gmail.com> wrote:
>> From: Bin Meng <bin.meng@windriver.com>
>>
>> The "clock-frequency" property of cpu nodes isn't required. Drop it.
>>
>> Signed-off-by: Bin Meng <bin.meng@windriver.com>
>> ---
>>
>> arch/riscv/boot/dts/microchip/microchip-mpfs.dtsi | 5 -----
>> 1 file changed, 5 deletions(-)
>>
> Ping?
Daire can you have a look at this and the other hart/clock related change?
>
> _______________________________________________
> linux-riscv mailing list
> linux-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2021-07-09 8:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 6:02 [PATCH 1/2] riscv: dts: microchip: Drop "clock-frequency" property of cpu nodes Bin Meng
2021-06-16 6:02 ` [PATCH 2/2] riscv: dts: microchip: Fix wrong interrupt numbers of DMA Bin Meng
2021-07-13 15:29 ` Conor.Dooley
2021-07-08 13:39 ` [PATCH 1/2] riscv: dts: microchip: Drop "clock-frequency" property of cpu nodes Bin Meng
2021-07-09 8:42 ` Conor.Dooley [this message]
2021-07-13 15:29 ` 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=48f0a6c0-13af-e2bd-6849-e84448f71b51@microchip.com \
--to=conor.dooley@microchip.com \
--cc=Daire.McNamara@microchip.com \
--cc=atish.patra@wdc.com \
--cc=bin.meng@windriver.com \
--cc=bmeng.cn@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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: 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