From: <Conor.Dooley@microchip.com>
To: <arnd@arndb.de>, <krzysztof.kozlowski@canonical.com>
Cc: <olof@lixom.net>, <arm@kernel.org>, <soc@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-samsung-soc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <krzk@kernel.org>,
<palmerdabbelt@google.com>, <paul.walmsley@sifive.com>,
<aou@eecs.berkeley.edu>, <linux-riscv@lists.infradead.org>
Subject: Re: [GIT PULL] riscv: dts: few cleanups for v5.16
Date: Thu, 21 Oct 2021 13:06:13 +0000 [thread overview]
Message-ID: <10f5244d-ba2a-33eb-72dc-77b2a7a0d101@microchip.com> (raw)
In-Reply-To: <CAK8P3a08QiwA4+zPGLt3xA=01HLiBcLcC4gM1+8N6uo5KMTQLw@mail.gmail.com>
On 21/10/2021 13:23, Arnd Bergmann wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> On Thu, Oct 21, 2021 at 11:09 AM Krzysztof Kozlowski
> <krzysztof.kozlowski@canonical.com> wrote:
>> Hi Arnd and Olof,
>>
>> I have an old patchset for RISC-V dts cleanups which I sent to mailing lists in
>> August 2021 (v1, v2), resent in September and pinged two times. They got some
>> review (from Alexandre Ghiti for SiFive, from Conor Dooley for Microchip) but
>> unfortunately Palmer (RISC-V maintainer) did not respond here.
Out of curiosity which series is this one? Is it the one with the
plic/clint changes?
Pretty sure that I have taken them in internally, but I am going to
submit a bunch
of changes to our device tree soon (tm) and want to make sure I have the
right
dependent series listed.
>>
>> The usual RISC-V patches go via Palmer to Linus and I am not planning to change
>> that, but I want to get these fixed.
>>
>> Could you grab these to soc tree?
> Sure, I can add them to a separate branch in the soc tree, in case the
> riscv maintainers
> take them after all. I notice that you have only Cc'd Palmer, but not
> the other two
> maintainers or the RISC-V mainling list. Adding them here to maybe get their
> attention.
>
> Arnd
>
> _______________________________________________
> linux-riscv mailing list
> linux-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2021-10-21 13:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211021090955.115005-1-krzysztof.kozlowski@canonical.com>
2021-10-21 12:23 ` [GIT PULL] riscv: dts: few cleanups for v5.16 Arnd Bergmann
2021-10-21 12:25 ` Krzysztof Kozlowski
2021-10-21 13:06 ` Conor.Dooley [this message]
2021-10-21 13:09 ` Krzysztof Kozlowski
2021-10-21 15:06 ` Palmer Dabbelt
2021-10-21 15:18 ` Arnd Bergmann
2021-10-21 15:35 ` Palmer Dabbelt
2021-10-22 8:55 ` Krzysztof Kozlowski
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=10f5244d-ba2a-33eb-72dc-77b2a7a0d101@microchip.com \
--to=conor.dooley@microchip.com \
--cc=aou@eecs.berkeley.edu \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=krzk@kernel.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.net \
--cc=palmerdabbelt@google.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: 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