From: Walker Chen <walker.chen@starfivetech.com>
To: Conor Dooley <conor@kernel.org>
Cc: <linux-riscv@lists.infradead.org>, <kernel@esmil.dk>
Subject: Re: Jh7110 DTS Patches
Date: Fri, 21 Jul 2023 10:04:28 +0800 [thread overview]
Message-ID: <cb65c688-6f88-2ac0-3a99-acef6f0bfe55@starfivetech.com> (raw)
In-Reply-To: <757fa8f2-4bab-07b3-13fd-aa983907bd77@starfivetech.com>
On 2023/7/21 10:00, Walker Chen wrote:
>
> On 2023/7/21 1:51, Conor Dooley wrote:
>> Hey Walker,
>>
>> I have picked up the patches that I can from the mailing list & they
>> should appear in tomorrow's iteration of linux-next. Could you get your
>> co-workers to resend whatever patches that depended on the syscons, PLLs
>> or STG etc clocks?
>>
>> Some were still on patchwork, eg the TDM audio, that I could not apply &
>> will need to be rebased. In particular, it'd be nice to get the eMMC
>> patches resent, as what I could find on patchwork was quite old.
>>
>> You can see what I have applied here:
>> https://git.kernel.org/pub/scm/linux/kernel/git/conor/linux.git/log/?h=riscv-dt-for-next
>>
>> Thanks,
>> Conor.
>
> Hi Conor,
>
> I have notified my co-workers that are responsible for these modules to resend dts patch ASAP.
> These patches are submitted together, there may be conflicts.
> Could you please help solve it then ?
> Thanks!
>
> Walker
>
The following modules require to resend dts patch:
DMA, GMAC, SDIO/EMMC, USB, Crypto, TRNG, TDM, MIPI CSI
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-07-21 2:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 17:51 Jh7110 DTS Patches Conor Dooley
2023-07-21 2:00 ` Walker Chen
2023-07-21 2:04 ` Walker Chen [this message]
2023-07-21 5:19 ` 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=cb65c688-6f88-2ac0-3a99-acef6f0bfe55@starfivetech.com \
--to=walker.chen@starfivetech.com \
--cc=conor@kernel.org \
--cc=kernel@esmil.dk \
--cc=linux-riscv@lists.infradead.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