public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: walker.chen@starfivetech.com
Cc: linux-riscv@lists.infradead.org, kernel@esmil.dk
Subject: Jh7110 DTS Patches
Date: Thu, 20 Jul 2023 18:51:34 +0100	[thread overview]
Message-ID: <20230720-product-cheese-9f0fe22cc485@spud> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 598 bytes --]

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.

[-- 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

             reply	other threads:[~2023-07-20 17:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-20 17:51 Conor Dooley [this message]
2023-07-21  2:00 ` Jh7110 DTS Patches Walker Chen
2023-07-21  2:04   ` Walker Chen
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=20230720-product-cheese-9f0fe22cc485@spud \
    --to=conor@kernel.org \
    --cc=kernel@esmil.dk \
    --cc=linux-riscv@lists.infradead.org \
    --cc=walker.chen@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: 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