Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: arnd@arndb.de
Cc: palmer@dabbelt.com, linux-riscv@lists.infradead.org, soc@kernel.org
Subject: Re: [GIT PULL] RISC-V Devicetrees for v6.4
Date: Tue, 11 Apr 2023 22:33:10 +0100	[thread overview]
Message-ID: <20230411-sacrifice-liable-524c033b70a8@spud> (raw)
In-Reply-To: <20230406-shank-impromptu-3d483bbc249f@spud>


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

On Thu, Apr 06, 2023 at 09:24:40PM +0100, Conor Dooley wrote:

> I may have another
> PR adding some of the peripherals (pmu, mmc) for the StarFive stuff
> that are already reviewed etc, but need a rebase on top of what
> actually got applied. Is that okay, or will the end of next week be
> too late for you?

FWIW, the patches didn't show up yet, and now it is too late for me :)

[-- 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-04-11 21:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-06 20:24 [GIT PULL] RISC-V Devicetrees for v6.4 Conor Dooley
2023-04-11 21:33 ` Conor Dooley [this message]

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=20230411-sacrifice-liable-524c033b70a8@spud \
    --to=conor@kernel.org \
    --cc=arnd@arndb.de \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.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