From: Conor Dooley <conor.dooley@microchip.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Conor Dooley <conor@kernel.org>, <soc@kernel.org>,
<linux-riscv@lists.infradead.org>
Subject: Re: [GIT PULL] RISC-V Devicetrees for v6.10
Date: Tue, 7 May 2024 11:21:41 +0100 [thread overview]
Message-ID: <20240507-concrete-come-2899fab0888e@wendy> (raw)
In-Reply-To: <b618c311-8925-4717-b6bf-f3699b106189@app.fastmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 948 bytes --]
On Tue, May 07, 2024 at 12:08:13PM +0200, Arnd Bergmann wrote:
> On Tue, May 7, 2024, at 11:58, Conor Dooley wrote:
> > On Tue, May 07, 2024 at 11:27:36AM +0200, Arnd Bergmann wrote:
> >> On Fri, May 3, 2024, at 17:24, Conor Dooley wrote:
> >> 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.
> >
> > The jh7xxx stuff does actually depend on another branch, although that
> > branch is fixes. Do you want that removed too? If you do, I'd say to
> > just drop the whole PR.
>
> As I wrote below, it's fine to have a branch based on a
> fixes branch, so please keep that part.
Cool, just wasn't sure if you were intentionally contradicting yourself
or if the "below" part had just been some general remarks. I'll try to
get a "revised" PR sent tomorrow.
Cheers,
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
next prev parent reply other threads:[~2024-05-07 10:22 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
2024-05-07 9:58 ` Conor Dooley
2024-05-07 10:08 ` Arnd Bergmann
2024-05-07 10:21 ` Conor Dooley [this message]
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=20240507-concrete-come-2899fab0888e@wendy \
--to=conor.dooley@microchip.com \
--cc=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