Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Conor Dooley" <conor@kernel.org>, soc@kernel.org
Cc: linux-riscv@lists.infradead.org
Subject: Re: [GIT PULL] RISC-V Devicetrees for v6.10
Date: Tue, 07 May 2024 11:27:36 +0200	[thread overview]
Message-ID: <5222e581-a189-4477-ba6a-edf4ce369eb0@app.fastmail.com> (raw)
In-Reply-To: <20240503-swimmer-botany-7368a8a17b1a@spud>

On Fri, May 3, 2024, at 17:24, Conor Dooley wrote:
> Hey Arnd,
>
> Please pull some dt updates for v6.10. The diff here is a little bigger
> than my tag implies, but I've done this on top of -fixes and wanted to
> make this obvious. I've also not really mentioned all the Kconfig stuff
> much as you'll get that in another branch.

Hi Conor,

I don't have a good feeling about pulling this one, given that it
is both really late and that it pulls in more dependencies than
we'd like to have.

I was really hoping to be done with new features last week
as I pulled in the other branches. There are two other DT
pull requests I got after that (amlogic and aspeed), which
I added to a "soc/dt-late" branch that I could send in the
second week of the merge window if everything goes well, but
those don't have the dependencies.

If you are able to extract the DT bits that don't depend
on other branches (jh7xxx, microchip, bindings and
new files) and resend those, I could still add them to the
same dt-late branch.

Basing a branch on top of a fixes branch is usually fine,
especially if those fixes were originally based on an
early -rc. I can also make exceptions when there are
complex dependencies between branches, but I need to be
able to plan for those and not get them just ahead of
the merge window.

     Arnd

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2024-05-07  9:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-03 15:24 [GIT PULL] RISC-V Devicetrees for v6.10 Conor Dooley
2024-05-07  9:27 ` Arnd Bergmann [this message]
2024-05-07  9:58   ` Conor Dooley
2024-05-07 10:08     ` Arnd Bergmann
2024-05-07 10:21       ` Conor Dooley
2024-05-07 12:15         ` Arnd Bergmann
2024-05-08 20: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=5222e581-a189-4477-ba6a-edf4ce369eb0@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=conor@kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --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